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-32433 Hot | 18 | 2025-04-29 22:54 UTC |
2 | CVE-2025-31324 Hot | 14 | 2025-04-29 10:06 UTC |
3 | CVE-2025-29927 Hot | 9 | 2025-04-29 16:06 UTC |
4 | CVE-2025-32432 | 6 | 2025-04-27 14:51 UTC |
5 | CVE-2025-31161 | 5 | 2025-04-25 07:28 UTC |
6 | CVE-2025-3914 | 3 | 2025-04-27 21:20 UTC |
7 | CVE-2025-3102 | 3 | 2025-04-26 05:01 UTC |
8 | CVE-2015-2797 | 2 | 2025-04-27 14:51 UTC |
9 | CVE-2025-24054 | 2 | 2025-04-27 08:51 UTC |
10 | CVE-2018-0114 | 2 | 2025-04-26 05:01 UTC |
11 | CVE-2025-24813 | 2 | 2025-04-27 14:51 UTC |
12 | CVE-2021-42287 | 2 | 2025-04-29 16:06 UTC |
13 | CVE-2025-30208 | 2 | 2025-04-24 15:23 UTC |
14 | CVE-2025-30406 | 2 | 2025-04-24 08:40 UTC |
15 | CVE-2019-5420 | 2 | 2025-04-26 05:01 UTC |
16 | CVE-2021-42278 | 2 | 2025-04-29 16:06 UTC |
17 | CVE-2016-2098 | 2 | 2025-04-26 05:01 UTC |
18 | CVE-2021-43857 | 2 | 2025-04-25 07:28 UTC |
19 | CVE-2022-25012 | 2 | 2025-04-29 04:51 UTC |
20 | CVE-2024-32830 | 2 | 2025-04-26 05:01 UTC |
21 | CVE-2022-3552 | 2 | 2025-04-27 21:20 UTC |
22 | CVE-2016-10033 | 2 | 2025-04-26 05:01 UTC |
23 | CVE-2023-1545 | 2 | 2025-04-26 05:01 UTC |
24 | CVE-2025-3248 | 2 | 2025-04-27 08:51 UTC |
25 | CVE-2025-29306 | 2 | 2025-04-25 07:28 UTC |
26 | CVE-2025-32965 | 2 | 2025-04-23 15:53 UTC |
27 | CVE-2024-27876 | 2 | 2025-04-24 08:40 UTC |
28 | CVE-2025-2825 | 2 | 2025-04-24 15:23 UTC |
29 | CVE-2022-29806 | 2 | 2025-04-28 15:30 UTC |
30 | CVE-2025-1974 | 2 | 2025-04-27 08:51 UTC |
31 | CVE-2019-19781 | 2 | 2025-04-27 14:51 UTC |
32 | CVE-2025-2120 | 1 | 2025-04-25 07:28 UTC |
33 | CVE-2024-40110 | 1 | 2025-04-28 22:43 UTC |
34 | CVE-2025-3243 | 1 | 2025-04-25 07:28 UTC |
35 | CVE-2025-31137 | 1 | 2025-04-23 15:53 UTC |
36 | CVE-2025-0927 | 1 | 2025-04-26 05:01 UTC |
37 | CVE-2022-42092 | 1 | 2025-04-27 21:20 UTC |
38 | CVE-2025-24132 | 1 | 2025-04-29 22:54 UTC |
39 | CVE-2025-30065 | 1 | 2025-04-28 22:43 UTC |
40 | CVE-2025-46657 | 1 | 2025-04-27 08:51 UTC |
41 | CVE-2024-3400 | 1 | 2025-04-29 16:06 UTC |
42 | CVE-2025-0401 | 1 | 2025-04-29 10:06 UTC |
43 | CVE-2024-8418 | 1 | 2025-04-28 09:30 UTC |
44 | CVE-2025-24091 | 1 | 2025-04-29 04:51 UTC |
45 | CVE-2025-2812 | 1 | 2025-04-25 07:28 UTC |
46 | CVE-2025-2294 | 1 | 2025-04-27 08:51 UTC |
47 | CVE-2025-46701 | 1 | 2025-04-29 04:51 UTC |
48 | CVE-2024-12905 | 1 | 2025-04-25 07:28 UTC |
49 | CVE-2024-12342 | 1 | 2025-04-29 22:54 UTC |
50 | CVE-2023-1389 | 1 | 2025-04-26 11:39 UTC |
51 | CVE-2025-3971 | 1 | 2025-04-28 09:30 UTC |
52 | CVE-2025-34028 | 1 | 2025-04-25 07:28 UTC |
53 | CVE-2024-31449 | 1 | 2025-04-27 14:51 UTC |
54 | CVE-2025-2301 | 1 | 2025-04-25 07:28 UTC |
55 | CVE-2017-8386 | 1 | 2025-04-27 14:51 UTC |
56 | CVE-2025-2404 | 1 | 2025-04-25 07:28 UTC |
57 | CVE-2023-46818 | 1 | 2025-04-27 21:20 UTC |
58 | CVE-2024-36587 | 1 | 2025-04-27 14:51 UTC |
59 | CVE-2025-43864 | 1 | 2025-04-27 14:51 UTC |
60 | CVE-2021-43798 | 1 | 2025-04-27 21:20 UTC |
61 | CVE-2024-42471 | 1 | 2025-04-25 07:28 UTC |
62 | CVE-2025-26014 | 1 | 2025-04-29 10:06 UTC |
63 | CVE-2023-30861 | 1 | 2025-04-25 07:28 UTC |
64 | CVE-2024-24919 | 1 | 2025-04-25 13:01 UTC |
65 | CVE-2025-24963 | 1 | 2025-04-23 08:27 UTC |
66 | CVE-2024-27956 | 1 | 2025-04-27 21:20 UTC |
67 | CVE-2024-7120 | 1 | 2025-04-24 15:23 UTC |
68 | CVE-2025-24252 | 1 | 2025-04-29 22:54 UTC |
69 | CVE-2023-27372 | 1 | 2025-04-29 16:06 UTC |
70 | CVE-2024-27808 | 1 | 2025-04-27 14:51 UTC |
71 | CVE-2024-31317 | 1 | 2025-04-27 08:51 UTC |
72 | CVE-2025-3776 | 1 | 2025-04-24 08:40 UTC |
73 | CVE-2024-49138 | 1 | 2025-04-23 21:23 UTC |
74 | CVE-2025-43865 | 1 | 2025-04-27 14:51 UTC |