|
automation
|
https://t.me/secdigestua/767
|
CVE-2023-41064
|
exploited |
2026-07-19 00:00:39
|
|
|
automation
|
https://t.me/secdigestua/767
|
CVE-2023-41061
|
exploited |
2026-07-19 00:00:39
|
|
|
automation
|
https://bsky.app/profile/offseq.bsky.social/post/3mqxhxek3hj2i
|
CVE-2026-12228
|
seen |
2026-07-19 00:00:36
|
|
|
automation
|
https://infosec.exchange/users/offseq/statuses/116943698895820998
|
CVE-2026-12228
|
seen |
2026-07-19 00:00:34
|
|
|
automation
|
https://t.me/secdigestua/386
|
CVE-2022-41099
|
exploited |
2026-07-19 00:00:30
|
|
|
automation
|
https://t.me/thehackernews/9544
|
CVE-2026-60137
|
published-proof-of-concept |
2026-07-19 00:00:28
|
|
|
automation
|
https://t.me/thehackernews/9544
|
CVE-2026-63030
|
published-proof-of-concept |
2026-07-19 00:00:28
|
|
|
automation
|
https://t.me/GithubRedTeam/93964
|
CVE-2026-43499
|
published-proof-of-concept |
2026-07-19 00:00:28
|
|
|
automation
|
Telegram/CpvaXe9fnUedm6bJYI1HwZHnl1nhf5QHGNliedV3hlmI4g
|
CVE-2026-1555
|
published-proof-of-concept |
2026-07-19 00:00:28
|
|
|
automation
|
Telegram/dSrPtZtWU5TOs_-aHsCLmxVeUwX3rOwZCiiXLuitYPBN2w
|
CVE-2026-58644
|
exploited |
2026-07-19 00:00:28
|
|