| CVE-2023-40476US | high8.8 | 2.26% (83rd) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.4 and 8dddb9ad2009705dfc3e50d59d7c56fc7314cfc3 |
| CVE-2023-40475US | high8.8 | 2.10% (82nd) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.4 and 8dddb9ad2009705dfc3e50d59d7c56fc7314cfc3 |
| CVE-2023-40474US | high8.8 | 2.10% (82nd) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.4 and 8dddb9ad2009705dfc3e50d59d7c56fc7314cfc3 |
| CVE-2023-37328US | high8.8 | 2.05% (81st) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22 and latest commit 6dff93acf69c40271a769aa2fa35efbcc2aeb9b4 |
| CVE-2023-44446US | high8.8 | 1.96% (80th) | — | ✗kein Fix | 2024-05-03 | ≤ 64a58c37acc564285a125f99570787fb678446c9 |
| CVE-2023-44429US | high8.8 | 1.81% (78th) | — | ✗kein Fix | 2024-05-03 | ≤ 4bda59f88d148a41b412705d4739342123a192d9 |
| CVE-2024-47606US | critical9.8 | 1.73% (77th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2023-37327US | high8.8 | 1.70% (77th) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.1 |
| CVE-2023-37329US | high8.8 | 1.64% (76th) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.2 |
| CVE-2024-4453US | high7.8 | 1.58% (75th) | — | ✗kein Fix | 2024-05-22 | ≤ fc0ef6ede6ceda8c89326b38899d4944a8091f40 and 1.24.0 |
| CVE-2024-0444US | high8.8 | 1.57% (75th) | — | ✗kein Fix | 2024-06-07 | ≤ ea6d602ccacee5f4bdf45b9f58eb0dc5320f3c07 |
| CVE-2023-50186US | high8.8 | 1.53% (75th) | — | ✗kein Fix | 2024-05-03 | ≤ bd4a9fde89e2549887e8a77d22ab027bed70d743 |
| CVE-2023-38103US | high8.8 | 1.52% (75th) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.3 |
| CVE-2023-38104US | high8.8 | 1.40% (72nd) | — | ✗kein Fix | 2024-05-03 | ≤ 1.22.3 |
| CVE-2024-47541US | high7.5 | 1.34% (71st) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47539US | critical9.8 | 1.32% (71st) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2026-3085US | — | 1.31% (71st) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2024-47538US | critical9.8 | 1.27% (70th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47607US | critical9.8 | 1.20% (68th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47777US | critical9.1 | 1.17% (67th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47776US | critical9.1 | 1.17% (67th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47775US | critical9.1 | 1.17% (67th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47597US | critical9.1 | 1.17% (67th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47596US | high7.5 | 1.15% (67th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47615US | critical9.8 | 1.13% (66th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47600US | critical9.1 | 1.13% (66th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47542US | high7.5 | 1.11% (66th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47546US | high7.5 | 1.08% (65th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47545US | high7.5 | 1.08% (65th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47544US | high7.5 | 1.08% (65th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47835US | high7.5 | 1.05% (64th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47540US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47537US | critical9.8 | 0.96% (61st) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47598US | critical9.1 | 0.95% (61st) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47602US | high7.5 | 0.92% (60th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47543US | high7.5 | 0.92% (60th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47834US | critical9.1 | 0.92% (60th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2025-3887US | — | 0.91% (60th) | — | ✗kein Fix | 2025-05-22 | ≤ 2e8b542145c1b11f8b8d927f6c679fd8028ceb60 |
| CVE-2024-47613US | critical9.8 | 0.90% (60th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2026-2921US | — | 0.88% (59th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2024-47603US | high7.5 | 0.87% (59th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47601US | high7.5 | 0.87% (59th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47599US | high7.5 | 0.87% (59th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47778US | high7.5 | 0.84% (58th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2024-47774US | critical9.1 | 0.83% (57th) | — | ✗kein Fix | 2024-12-12 | ≤ < 1.24.10 |
| CVE-2026-3083US | — | 0.82% (57th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2026-3082US | — | 0.82% (57th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2026-2920US | — | 0.79% (56th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2026-2923US | — | 0.74% (55th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |
| CVE-2026-3081US | — | 0.44% (38th) | — | ✗kein Fix | 2026-03-16 | ≤ 1c6e163aa33962f5ee4a87d29319ccdd5cb67612 |