GitHub CVE statistics

Below you'll find the most talked-about vulnerabilities on GitHub for the selected time window. We scan every incoming repository name and description, extract CVE identifiers, and rank them by how often developers reference them. The fresher the CVE and the higher its rank, the more likely it is that proof-of-concept code, exploit scripts or mitigation tips are circulating right now.

How to act on this data
  • If a CVE in the Top 10 affects your stack, prioritise patching and monitor for exploitation attempts.
  • Click a CVE ID to open its NVD page for full details, CVSS scores and known mitigations.
  • Switch the timeframe to spot emerging threats or long-term trends.
Rank CVE Repo count Last seen
101 CVE-2024-38474 Hot 1 2025-04-16 18:03 UTC
102 CVE-2024-26229 Hot 1 2025-04-16 18:03 UTC
103 CVE-2020-1938 Hot 1 2025-04-16 18:01 UTC
104 CVE-2019-5786 1 2025-04-16 18:01 UTC
105 CVE-2021-2109 1 2025-04-16 18:01 UTC
106 CVE-2020-0601 1 2025-04-16 18:01 UTC
107 CVE-2019-17558 1 2025-04-16 18:01 UTC
108 CVE-2024-35250 1 2025-04-16 18:03 UTC
109 CVE-2020-1472 1 2025-04-16 18:01 UTC
110 CVE-2021-42287 1 2025-04-16 18:01 UTC
111 CVE-2024-38473 1 2025-04-16 18:03 UTC
112 CVE-2024-34342 1 2025-04-16 18:01 UTC
113 CVE-2022-46689 1 2025-04-16 18:01 UTC
114 CVE-2019-12587 1 2025-04-16 18:01 UTC
115 CVE-2025-27636 1 2025-04-16 18:03 UTC
116 CVE-2019-12586 1 2025-04-16 18:01 UTC
117 CVE-2020-2551 1 2025-04-16 18:01 UTC
118 CVE-2024-25600 1 2025-04-16 18:03 UTC
119 CVE-2024-32002 1 2025-04-16 18:01 UTC
120 CVE-2024-43609 1 2025-04-16 18:03 UTC
121 CVE-2021-25646 1 2025-04-16 18:01 UTC
122 CVE-2020-2883 1 2025-04-16 18:01 UTC
123 CVE-2024-39573 1 2025-04-16 18:03 UTC