|
automation
|
https://t.me/reverseame/3369
|
CVE-2023-29383
|
published-proof-of-concept |
2026-08-02 17:00:04
|
|
|
automation
|
https://t.me/reverseame/3373
|
CVE-2021-38001
|
published-proof-of-concept |
2026-08-02 17:00:04
|
|
|
automation
|
https://t.me/reverseame/3385
|
CVE-2023-28231
|
published-proof-of-concept |
2026-08-02 17:00:04
|
|
|
automation
|
https://t.me/reverseame/3351
|
CVE-2019-5736
|
published-proof-of-concept |
2026-08-02 17:00:04
|
|
|
automation
|
https://t.me/reverseame/3352
|
CVE-2023-21707
|
published-proof-of-concept |
2026-08-02 17:00:04
|
|
|
automation
|
https://bsky.app/profile/nixpkgssecuritychanges.gerbet.me/post/3ms4f7ogxqf2c
|
CVE-2026-60075
|
seen |
2026-08-02 16:20:04
|
|
|
automation
|
https://bsky.app/profile/nixpkgssecuritychanges.gerbet.me/post/3ms4f7ogxqf2c
|
CVE-2026-60074
|
seen |
2026-08-02 16:20:04
|
|
|
automation
|
https://t.me/hackersmeet0/1011
|
CVE-2019-18426
|
seen |
2026-08-02 16:19:36
|
|
|
automation
|
https://bsky.app/profile/newssecia.bsky.social/post/3ms4f5kn6af22
|
CVE-2024-40422
|
seen |
2026-08-02 16:18:52
|
|
|
automation
|
Telegram/K0a89wronOXzEhnmD7Qf737NDEZfjjpirHYYWg73RxkrcA
|
CVE-2022-2190
|
published-proof-of-concept |
2026-08-02 16:13:05
|
|