Sightings
| Author | Source | Vulnerability | Type | Date | Other |
|---|---|---|---|---|---|
| automation | Telegram/0FkprSeQP0YKYs2oblBz5o7rDVlvxUyLHL4sJJZN3ykZN_DT | CVE-2024-11936 | seen | 2025-02-06 02:42:29 | |
| automation | https://t.me/cvedetector/16414 | CVE-2024-11936 | seen | 2025-01-26 15:44:37 | |
| automation | https://mastodon.social/users/CyberSignaler/statuses/113895204622965670 | CVE-2024-11936 | seen | 2025-01-26 14:48:23 | |
| automation | https://bsky.app/profile/cve.skyfleet.blue/post/3lgno3rmkhg2w | CVE-2024-11936 | seen | 2025-01-26 14:45:41 | |
| automation | https://bsky.app/profile/cve.skyfleet.blue/post/3lgno3riyo62i | CVE-2024-11936 | seen | 2025-01-26 14:45:41 | |
| automation | https://t.me/DarkWebInformer_CVEAlerts/3132 | CVE-2024-11936 | seen | 2025-01-26 13:06:17 | |
| automation | https://bsky.app/profile/cve-notifications.bsky.social/post/3lgnfpw4ybh2h | CVE-2024-11936 | seen | 2025-01-26 12:15:53 | |
| automation | https://infosec.exchange/users/cve/statuses/113894370004265885 | CVE-2024-11936 | seen | 2025-01-26 11:16:07 |
displaying 1 - 8 sightings in total 8
If a line is highlighted in yellow, it indicates that the vulnerability advisory has not yet been published.