|
sync_user
|
https://t.me/reverseame/4870
|
CVE-2024-10979
|
published-proof-of-concept |
2026-08-02 04:25:50
|
|
|
sync_user
|
https://t.me/reverseame/4841
|
CVE-2024-21216
|
seen |
2026-08-02 04:17:10
|
|
|
sync_user
|
https://t.me/reverseame/4836
|
CVE-2024-0012
|
published-proof-of-concept |
2026-08-02 04:15:00
|
|
|
sync_user
|
https://t.me/reverseame/4831
|
CVE-2024-47575
|
published-proof-of-concept |
2026-08-02 04:08:44
|
|
|
sync_user
|
https://t.me/reverseame/4831
|
CVE-2024-23113
|
published-proof-of-concept |
2026-08-02 04:08:44
|
|
|
sync_user
|
https://t.me/reverseame/4813
|
CVE-2024-8957
|
published-proof-of-concept |
2026-08-02 04:06:34
|
|
|
sync_user
|
https://t.me/reverseame/4813
|
CVE-2024-8956
|
published-proof-of-concept |
2026-08-02 04:04:24
|
|
|
sync_user
|
https://t.me/reverseame/4780
|
CVE-2024-23113
|
published-proof-of-concept |
2026-08-02 04:04:23
|
|
|
sync_user
|
https://infosec.exchange/users/vuldb/statuses/117023665141420912
|
CVE-2026-18556
|
seen |
2026-08-02 03:27:01
|
|
|
sync_user
|
https://t.me/reverseame/5155
|
CVE-2025-2775
|
published-proof-of-concept |
2026-08-02 03:00:06
|
|