Community
Sightings
| Author | Source | Vulnerability | Type | Date | Other |
|---|---|---|---|---|---|
| automation | https://t.me/hacking_Attack/106078 | CVE-2017-5638 | exploited | 2026-09-05 01:00:28 | |
| automation | https://t.me/hacking_Attack/106076 | CVE-2017-5638 | published-proof-of-concept | 2026-09-05 01:00:27 | |
| automation | https://t.me/hacking_Attack/106078 | CVE-2017-5638 | exploited | 2026-09-04 13:00:04 | |
| automation | https://t.me/hacking_Attack/106076 | CVE-2017-5638 | published-proof-of-concept | 2026-09-04 13:00:04 | |
| automation | Telegram/1Sqk7SiaOozsfKPKNBJ8D4wLm4oiagj85GLZSROTXIrOhqI | CVE-2017-5638 | seen | 2026-09-04 00:00:42 | |
| automation | Telegram/1Sqk7SiaOozsfKPKNBJ8D4wLm4oiagj85GLZSROTXIrOhqI | CVE-2017-5638 | seen | 2026-09-03 17:00:05 | |
| automation | Telegram/V5hKn0oJ2nGQvFUOA8vMmIzpE0-LTzLZfzF3v7e7Ud5xOzo | CVE-2017-5638 | published-proof-of-concept | 2026-09-03 00:00:53 | |
| automation | Telegram/FxPwD2QYmiA5ZVhY8rKhgPR6q1a7u8sU2ARM9Vm3CjRJJs0 | CVE-2017-5638 | published-proof-of-concept | 2026-09-03 00:00:43 | |
| automation | Telegram/FxPwD2QYmiA5ZVhY8rKhgPR6q1a7u8sU2ARM9Vm3CjRJJs0 | CVE-2017-5638 | seen | 2026-09-02 05:00:04 | |
| automation | https://t.me/hacking_Attack/106076 | CVE-2017-5638 | seen | 2026-09-02 01:01:17 |
displaying 1 - 10 sightings in total 232
If a line is highlighted in yellow, it indicates that the vulnerability advisory has not yet been published.