Community
Sightings
| Author | Source | Vulnerability | Type | Date | Other |
|---|---|---|---|---|---|
| automation | https://bsky.app/profile/cve.skyfleet.blue/post/3mro7glu6nf2x | CVE-2026-53668 | seen | 2026-07-28 00:59:17 | |
| automation | Telegram/ChI_-_yuP3aEKC_gSwO4QBcx90clvJ_NicXYpP6AzBpj5p0 | CVE-2026-5366 | published-proof-of-concept | 2026-07-18 02:00:05 | |
| automation | Telegram/om3YhtaPu5txmcqgS2vE6wxr9r90wWmyuf596mxiJ-5mabI | CVE-2026-5366 | published-proof-of-concept | 2026-07-18 02:00:05 | |
| automation | Telegram/om3YhtaPu5txmcqgS2vE6wxr9r90wWmyuf596mxiJ-5mabI | CVE-2026-5366 | seen | 2026-07-16 19:00:29 | |
| automation | Telegram/ChI_-_yuP3aEKC_gSwO4QBcx90clvJ_NicXYpP6AzBpj5p0 | CVE-2026-5366 | seen | 2026-07-16 19:00:29 | |
| automation | https://t.me/GithubRedTeam/90845 | CVE-2026-5366 | published-proof-of-concept | 2026-07-15 00:00:21 | |
| automation | https://t.me/GithubRedTeam/90845 | CVE-2026-5366 | seen | 2026-07-13 22:00:18 | |
| automation | https://bsky.app/profile/kriptabiz.bsky.social/post/3mpnklw3gq72y | CVE-2026-5366 | seen | 2026-07-02 07:56:04 | |
| automation | https://infosec.exchange/users/offseq/statuses/116802848530420895 | CVE-2026-53662 | seen | 2026-06-24 03:00:29 | |
| automation | https://infosec.exchange/users/offseq/statuses/116785154318795848 | CVE-2026-5366 | seen | 2026-06-21 00:00:42 |
displaying 1 - 10 sightings in total 12
If a line is highlighted in yellow, it indicates that the vulnerability advisory has not yet been published.