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.
Rank | CVE | Repo count | Last seen |
---|---|---|---|
1 | CVE-2025-0282 Hot | 6 | 2025-04-16 18:03 UTC |
2 | CVE-2025-24813 Hot | 5 | 2025-04-16 18:03 UTC |
3 | CVE-2018-20250 Hot | 4 | 2025-04-16 18:03 UTC |
4 | CVE-2025-24016 | 4 | 2025-04-16 18:03 UTC |
5 | CVE-2021-21972 | 4 | 2025-04-16 18:01 UTC |
6 | CVE-2025-1974 | 4 | 2025-04-16 18:03 UTC |
7 | CVE-2016-5195 | 4 | 2025-04-16 18:01 UTC |
8 | CVE-2020-0796 | 4 | 2025-04-16 18:01 UTC |
9 | CVE-2022-0847 | 3 | 2025-04-16 18:01 UTC |
10 | CVE-2021-3156 | 3 | 2025-04-16 18:01 UTC |
11 | CVE-2017-11882 | 3 | 2025-04-16 18:01 UTC |
12 | CVE-2024-6387 | 3 | 2025-04-16 18:03 UTC |
13 | CVE-2017-7494 | 3 | 2025-04-16 18:01 UTC |
14 | CVE-2021-4034 | 3 | 2025-04-16 18:01 UTC |
15 | CVE-2019-5736 | 3 | 2025-04-16 18:01 UTC |
16 | CVE-2025-24799 | 3 | 2025-04-17 08:31 UTC |
17 | CVE-2025-43921 | 2 | 2025-04-19 23:43 UTC |
18 | CVE-2023-38831 | 2 | 2025-04-16 18:01 UTC |
19 | CVE-2025-0411 | 2 | 2025-04-16 18:03 UTC |
20 | CVE-2024-38063 | 2 | 2025-04-16 18:01 UTC |
21 | CVE-2024-7479 | 2 | 2025-04-16 18:03 UTC |
22 | CVE-2025-24514 | 2 | 2025-04-16 18:03 UTC |
23 | CVE-2025-30208 | 2 | 2025-04-16 18:03 UTC |
24 | CVE-2020-14882 | 2 | 2025-04-16 18:01 UTC |
25 | CVE-2023-7028 | 2 | 2025-04-16 18:01 UTC |
26 | CVE-2025-43919 | 2 | 2025-04-19 23:43 UTC |
27 | CVE-2024-4577 | 2 | 2025-04-16 18:03 UTC |
28 | CVE-2024-49113 | 2 | 2025-04-16 18:03 UTC |
29 | CVE-2018-7600 | 2 | 2025-04-16 18:01 UTC |
30 | CVE-2020-1350 | 2 | 2025-04-16 18:01 UTC |
31 | CVE-2021-1732 | 2 | 2025-04-16 18:01 UTC |
32 | CVE-2021-40444 | 2 | 2025-04-16 18:01 UTC |
33 | CVE-2024-4367 | 2 | 2025-04-16 18:01 UTC |
34 | CVE-2018-8120 | 2 | 2025-04-16 18:01 UTC |
35 | CVE-2024-1086 | 2 | 2025-04-16 18:01 UTC |
36 | CVE-2015-7547 | 2 | 2025-04-16 18:01 UTC |
37 | CVE-2025-43920 | 2 | 2025-04-19 23:43 UTC |
38 | CVE-2017-0785 | 2 | 2025-04-16 18:01 UTC |
39 | CVE-2017-8570 | 2 | 2025-04-16 18:01 UTC |
40 | CVE-2021-44228 | 2 | 2025-04-16 18:01 UTC |
41 | CVE-2024-30078 | 2 | 2025-04-16 18:03 UTC |
42 | CVE-2025-29927 | 2 | 2025-04-16 18:03 UTC |
43 | CVE-2025-1098 | 2 | 2025-04-16 18:03 UTC |
44 | CVE-2024-38077 | 2 | 2025-04-16 18:03 UTC |
45 | CVE-2023-4911 | 2 | 2025-04-16 18:01 UTC |
46 | CVE-2018-15473 | 2 | 2025-04-16 18:01 UTC |
47 | CVE-2024-23897 | 2 | 2025-04-16 18:03 UTC |
48 | CVE-2024-0044 | 2 | 2025-04-16 18:03 UTC |
49 | CVE-2024-38200 | 2 | 2025-04-16 18:03 UTC |
50 | CVE-2025-0108 | 2 | 2025-04-16 18:03 UTC |
51 | CVE-2021-31166 | 2 | 2025-04-16 18:01 UTC |
52 | CVE-2024-21413 | 2 | 2025-04-16 18:03 UTC |
53 | CVE-2024-49138 | 2 | 2025-04-16 18:03 UTC |
54 | CVE-2022-40684 | 2 | 2025-04-16 18:01 UTC |
55 | CVE-2025-24071 | 2 | 2025-04-16 18:03 UTC |
56 | CVE-2024-7481 | 2 | 2025-04-16 18:03 UTC |
57 | CVE-2018-0802 | 2 | 2025-04-16 18:01 UTC |
58 | CVE-2025-21333 | 2 | 2025-04-16 18:03 UTC |
59 | CVE-2023-21768 | 2 | 2025-04-16 18:01 UTC |
60 | CVE-2025-32433 | 2 | 2025-04-19 23:43 UTC |
61 | CVE-2025-22457 | 2 | 2025-04-16 18:03 UTC |
62 | CVE-2025-1097 | 2 | 2025-04-16 18:03 UTC |
63 | CVE-2025-21298 | 2 | 2025-04-16 18:01 UTC |
64 | CVE-2023-38146 | 1 | 2025-04-16 18:01 UTC |
65 | CVE-2025-21420 | 1 | 2025-04-16 18:03 UTC |
66 | CVE-2018-14847 | 1 | 2025-04-16 18:01 UTC |
67 | CVE-2016-10033 | 1 | 2025-04-16 18:01 UTC |
68 | CVE-2024-38472 | 1 | 2025-04-16 18:03 UTC |
69 | CVE-2019-12588 | 1 | 2025-04-16 18:01 UTC |
70 | CVE-2025-0401 | 1 | 2025-04-16 18:03 UTC |
71 | CVE-2024-38476 | 1 | 2025-04-16 18:03 UTC |
72 | CVE-2024-30051 | 1 | 2025-04-16 18:03 UTC |
73 | CVE-2023-38709 | 1 | 2025-04-16 18:03 UTC |
74 | CVE-2022-26134 | 1 | 2025-04-16 18:01 UTC |
75 | CVE-2024-30088 | 1 | 2025-04-16 18:03 UTC |
76 | CVE-2020-11444 | 1 | 2025-04-16 18:01 UTC |
77 | CVE-2018-2025 | 1 | 2025-04-16 18:03 UTC |
78 | CVE-2019-0708 | 1 | 2025-04-16 18:01 UTC |
79 | CVE-2025-26125 | 1 | 2025-04-16 18:03 UTC |
80 | CVE-2019-11043 | 1 | 2025-04-16 18:01 UTC |
81 | CVE-2024-21338 | 1 | 2025-04-16 18:03 UTC |
82 | CVE-2021-22986 | 1 | 2025-04-16 18:01 UTC |
83 | CVE-2019-18634 | 1 | 2025-04-16 18:01 UTC |
84 | CVE-2025-24118 | 1 | 2025-04-16 18:03 UTC |
85 | CVE-2022-22965 | 1 | 2025-04-16 18:01 UTC |
86 | CVE-2024-20017 | 1 | 2025-04-16 18:03 UTC |
87 | CVE-2020-25078 | 1 | 2025-04-16 18:01 UTC |
88 | CVE-2024-3094 | 1 | 2025-04-16 18:03 UTC |
89 | CVE-2024-38477 | 1 | 2025-04-16 18:03 UTC |
90 | CVE-2018-4087 | 1 | 2025-04-16 18:01 UTC |
91 | CVE-2021-26885 | 1 | 2025-04-16 18:01 UTC |
92 | CVE-2020-2555 | 1 | 2025-04-16 18:01 UTC |
93 | CVE-2024-21111 | 1 | 2025-04-16 18:03 UTC |
94 | CVE-2020-10204 | 1 | 2025-04-16 18:01 UTC |
95 | CVE-2020-14883 | 1 | 2025-04-16 18:01 UTC |
96 | CVE-2021-3129 | 1 | 2025-04-16 18:01 UTC |
97 | CVE-2019-6340 | 1 | 2025-04-16 18:01 UTC |
98 | CVE-2021-42278 | 1 | 2025-04-16 18:01 UTC |
99 | CVE-2020-10199 | 1 | 2025-04-16 18:01 UTC |
100 | CVE-2024-38475 | 1 | 2025-04-16 18:03 UTC |