|
automation
|
https://t.me/reverseame/1942
|
CVE-2021-31956
|
published-proof-of-concept |
2026-08-03 03:02:13
|
|
|
automation
|
https://t.me/reverseame/1923
|
CVE-2021-42278
|
published-proof-of-concept |
2026-08-03 03:02:13
|
|
|
automation
|
https://t.me/reverseame/1923
|
CVE-2021-42287
|
published-proof-of-concept |
2026-08-03 03:02:13
|
|
|
automation
|
https://t.me/reverseame/1912
|
CVE-2021-44228
|
exploited |
2026-08-03 03:02:13
|
|
|
automation
|
https://t.me/reverseame/1914
|
CVE-2021-44228
|
exploited |
2026-08-03 03:02:13
|
|
|
automation
|
https://github.com/projectdiscovery/nuclei-templates/tree/main/http/cves/2019/CVE-2019-14793.yaml
|
CVE-2019-14793
|
confirmed |
2026-08-03 03:00:04
|
|
|
automation
|
https://t.me/reverseame/4597
|
CVE-2024-21338
|
published-proof-of-concept |
2026-08-03 02:40:50
|
|
|
automation
|
https://infosec.exchange/users/vuldb/statuses/117029256627432016
|
CVE-2026-68578
|
seen |
2026-08-03 02:39:01
|
|
|
automation
|
https://t.me/GithubRedTeam/96351
|
CVE-2026-32746
|
published-proof-of-concept |
2026-08-03 02:36:33
|
|
|
automation
|
Telegram/J3IW9JUNrZQpqIAdEWhkq9xiU68g28q9BOBiyI96fMrzQ8w
|
CVE-2025-48932
|
published-proof-of-concept |
2026-08-03 02:34:23
|
|