|
automation
|
https://t.me/hacking_Attack/156018
|
CVE-2025-31080
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/156020
|
CVE-2025-31080
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/153696
|
CVE-2020-28036
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/155018
|
CVE-2025-24993
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/155020
|
CVE-2025-24993
|
seen |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/155726
|
CVE-2025-29927
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
https://github.com/projectdiscovery/nuclei-templates/tree/main/http/cves/2026/CVE-2026-57582.yaml
|
CVE-2026-57582
|
confirmed |
2026-09-03 12:00:05
|
|
|
automation
|
https://t.me/hacking_Attack/152670
|
CVE-2025-0411
|
published-proof-of-concept |
2026-09-03 12:00:05
|
|
|
automation
|
Telegram/wjGJNcgiCtazOObm08zBWnjh0cnGBFnktQF1xuBs3F9UCdI
|
CVE-2026-38577
|
seen |
2026-09-03 12:00:05
|
|
|
automation
|
Telegram/wjGJNcgiCtazOObm08zBWnjh0cnGBFnktQF1xuBs3F9UCdI
|
CVE-2025-9974
|
seen |
2026-09-03 12:00:05
|
|