|
automation
|
https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/0c75f2c5-b09c-4f9c-aba7-7f387979219d
|
CVE-2025-56520
|
exploited |
2026-10-06 11:00:38
|
|
|
automation
|
https://bsky.app/profile/crowdsec.bsky.social/post/3meyajahdkc23
|
CVE-2025-56520
|
seen |
2026-02-16 14:17:48
|
|
|
automation
|
https://bsky.app/profile/crowdsec.bsky.social/post/3meyabqmnpc23
|
CVE-2025-56520
|
seen |
2026-02-16 14:13:37
|
|
|
automation
|
https://bsky.app/profile/beikokucyber.bsky.social/post/3merfr6lr6w2k
|
CVE-2025-56520
|
seen |
2026-02-13 21:03:09
|
|
|
automation
|
https://bsky.app/profile/beikokucyber.bsky.social/post/3mcv2l36vqa2k
|
CVE-2025-56520
|
seen |
2026-01-20 21:03:06
|
|
|
automation
|
https://github.com/projectdiscovery/nuclei-templates/tree/main/http/cves/2025/CVE-2025-56520.yaml
|
CVE-2025-56520
|
confirmed |
2026-01-20 04:04:17
|
|
|
automation
|
Telegram/JTPMSiIeITdIAco4zqe7AJCP4y0ey6zBic2rAw1xqSNEfqQ
|
CVE-2025-56527
|
published-proof-of-concept |
2025-11-14 15:00:07
|
|
|
automation
|
Telegram/JTPMSiIeITdIAco4zqe7AJCP4y0ey6zBic2rAw1xqSNEfqQ
|
CVE-2025-56526
|
published-proof-of-concept |
2025-11-14 15:00:07
|
|
|
automation
|
Telegram/ZUTGmtSEE7XNsqh5MFfP6oM9uk0-KZeASr5gwV6QxuDkHtI
|
CVE-2025-56522
|
published-proof-of-concept |
2025-10-27 09:00:05
|
|
|
automation
|
Telegram/ZUTGmtSEE7XNsqh5MFfP6oM9uk0-KZeASr5gwV6QxuDkHtI
|
CVE-2025-56521
|
published-proof-of-concept |
2025-10-27 09:00:05
|
|