|
sync_user
|
https://t.me/reverseame/622
|
CVE-2020-28949
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/582
|
CVE-2020-16898
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/608
|
CVE-2020-8276
|
seen |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/562
|
CVE-2020-13629
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/570
|
CVE-2020-15157
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/579
|
CVE-2020-16938
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/541
|
CVE-2020-8243
|
published-proof-of-concept |
2026-08-04 00:00:36
|
|
|
sync_user
|
https://t.me/reverseame/550
|
CVE-2020-14871
|
published-proof-of-concept |
2026-08-04 00:00:35
|
|
|
sync_user
|
https://t.me/GithubRedTeam/96442
|
CVE-2026-43499
|
published-proof-of-concept |
2026-08-04 00:00:35
|
|
|
sync_user
|
https://t.me/information_security_channel/55668
|
CVE-2026-18577
|
exploited |
2026-08-04 00:00:35
|
|