| CVE-2026-69084US | — | 1.57% (75th) | Exploit | ✓0.0.0-20260721002947-23a17d44b5f3 | 2026-08-03 | < 0.0.0-20260721002947-23a17d44b5f3 |
| CVE-2026-33067US | critical9.0 | 0.56% (46th) | Exploit | ✓0.0.0-20260317012524-fe4523fff2c8 | 2026-03-20 | < 0.0.0-20260317012524-fe4523fff2c8 |
| CVE-2026-69083US | — | 0.47% (41st) | Exploit | ✓0.0.0-20260721004815-cf42dd5680c8 | 2026-08-03 | < 0.0.0-20260721004815-cf42dd5680c8 |
| CVE-2026-54069US | — | 7.47% (94th) | — | ✓0.0.0-20260628153353-2d5d72223df4 | 2026-06-24 | < 0.0.0-20260628153353-2d5d72223df4 |
| CVE-2026-54068US | —OT erhöht | 4.32% (91st) | — | ✓0.0.0-20260628153353-2d5d72223df4 | 2026-06-24 | < 0.0.0-20260628153353-2d5d72223df4 |
| CVE-2026-33476US | — | 3.26% (88th) | — | ✗kein Fix | 2026-03-20 | 2 Versionen |
| CVE-2026-54066US | —OT erhöht | 2.17% (82nd) | — | ✓0.0.0-20260628153353-2d5d72223df4 | 2026-06-24 | < 0.0.0-20260628153353-2d5d72223df4 |
| CVE-2026-69085US | — | 1.39% (72nd) | — | ✓0.0.0-20260721043339-eef10568384e | 2026-08-03 | < 0.0.0-20260721043339-eef10568384e |
| CVE-2026-34453US | —OT erhöht | 1.23% (69th) | — | ✓3.6.2 | 2026-03-31 | 2 Versionen |
| CVE-2026-25539US | high7.2 | 1.12% (66th) | — | ✗kein Fix | 2026-02-04 | 2 Versionen |
| CVE-2026-30869US | critical9.8 | 1.11% (66th) | — | ✓3.5.10 | 2026-03-10 | 2 Versionen |
| CVE-2026-32751US | critical9.0 | 0.83% (57th) | — | ✗kein Fix | 2026-03-19 | 2 Versionen |
| CVE-2024-55657US | high7.5 | 0.74% (54th) | — | ✗kein Fix | 2024-12-12 | 2 Versionen |
| CVE-2026-56395US | — | 0.70% (52nd) | — | ✓0.0.0-20260317012524-fe4523fff2c8 | 2026-06-21 | 2 Versionen |
| CVE-2026-33670US | high7.5 | 0.67% (52nd) | — | ✗kein Fix | 2026-03-26 | 2 Versionen |
| CVE-2026-29183US | medium6.1 | 0.64% (50th) | — | ✓0.0.0-20260304034809-d68bd5a79391 | 2026-03-06 | < 0.0.0-20260304034809-d68bd5a79391 |
| CVE-2025-21609US | critical9.1 | 0.63% (50th) | — | ✗kein Fix | 2025-01-03 | — |
| CVE-2024-55660US | critical9.8 | 0.62% (50th) | — | ✗kein Fix | 2024-12-12 | 2 Versionen |
| CVE-2026-23850US | high7.5 | 0.62% (49th) | — | ✓0.0.0-20260118092326-b2274baba2e1 | 2026-01-19 | < 0.0.0-20260118092326-b2274baba2e1 |
| CVE-2024-55658US | high7.5 | 0.60% (49th) | — | ✗kein Fix | 2024-12-12 | 2 Versionen |
| CVE-2026-33066US | critical9.0 | 0.60% (48th) | — | ✓0.0.0-20260314111550-b382f50e1880 | 2026-03-20 | < 0.0.0-20260314111550-b382f50e1880 |
| CVE-2026-25992US | — | 0.59% (48th) | — | ✗kein Fix | 2026-02-10 | 2 Versionen |
| CVE-2026-65607US | — | 0.59% (48th) | — | ✓0.0.0-20260510110132-b763d787d1f2 | 2026-07-23 | < 0.0.0-20260510110132-b763d787d1f2 |
| CVE-2026-50551US | — | 0.56% (46th) | — | ✓0.0.0-20260628153353-2d5d72223df4 | 2026-06-24 | < 0.0.0-20260628153353-2d5d72223df4 |
| CVE-2026-32767US | —OT erhöht | 0.55% (46th) | — | ✗kein Fix | 2026-03-20 | 2 Versionen |
| CVE-2026-73054US | — | 0.54% (45th) | — | ✓0.0.0-20260731131820-67bc300b6ea6 | 2026-08-15 | 2 Versionen |
| CVE-2026-39846US | critical9.0 | 0.54% (45th) | — | ✓0.0.0-20260407035653-2f416e5253f1 | 2026-04-07 | < 0.0.0-20260407035653-2f416e5253f1 |
| CVE-2026-72810US | —OT erhöht | 0.54% (45th) | — | ✓0.0.0-20260723013612-ba948639d7f6 | 2026-08-14 | < 0.0.0-20260723013612-ba948639d7f6 |
| CVE-2026-68584US | —OT erhöht | 0.53% (45th) | — | ✓0.0.0-20260721020826-2d069dce84a2 | 2026-08-03 | < 0.0.0-20260721020826-2d069dce84a2 |
| CVE-2026-33669US | high7.5 | 0.53% (45th) | — | ✗kein Fix | 2026-03-26 | 2 Versionen |
| CVE-2026-69086US | — | 0.53% (45th) | — | ✓0.0.0-20260720151813-0f5a0e7c67b0 | 2026-08-03 | < 0.0.0-20260720151813-0f5a0e7c67b0 |
| CVE-2026-23851US | medium6.5 | 0.52% (44th) | — | ✓0.0.0-20260118092521-f8f4b517077b | 2026-01-19 | < 0.0.0-20260118092521-f8f4b517077b |
| CVE-2026-31809US | medium6.1 | 0.52% (44th) | — | ✓0.0.0-20260310025236-297bd526708f | 2026-03-10 | < 0.0.0-20260310025236-297bd526708f |
| CVE-2026-33203US | —OT erhöht | 0.52% (44th) | — | ✓3.6.2 | 2026-03-20 | 2 Versionen |
| CVE-2026-44670US | —OT erhöht | 0.51% (43rd) | — | ✓0.0.0-20260512140701-d7b77d945e0d | 2026-05-14 | < 0.0.0-20260512140701-d7b77d945e0d |
| CVE-2026-44588US | —OT erhöht | 0.51% (43rd) | — | ✗kein Fix | 2026-05-14 | 2 Versionen |
| CVE-2026-33194US | — | 0.51% (43rd) | — | ✓3.6.2 | 2026-03-20 | 2 Versionen |
| CVE-2026-34449US | — | 0.50% (43rd) | — | ✓3.6.2 | 2026-03-31 | 2 Versionen |
| CVE-2026-56397US | — | 0.50% (42nd) | — | ✓0.0.0-20260317012524-fe4523fff2c8 | 2026-06-21 | 2 Versionen |
| CVE-2026-34448US | — | 0.49% (42nd) | — | ✓3.6.2 | 2026-03-31 | 2 Versionen |
| CVE-2026-59834US | — | 0.48% (41st) | — | ✓0.0.0-20260704035518-d0f0fe146fb0 | 2026-07-09 | < 0.0.0-20260704035518-d0f0fe146fb0 |
| CVE-2026-82651US | medium4.9OT erhöht | 0.48% (41st) | — | ✓0.0.0-20260816034002-035bf9a8c311 | 2026-08-30 | < 0.0.0-20260816034002-035bf9a8c311 |
| CVE-2026-34605US | medium6.1 | 0.47% (40th) | — | ✓0.0.0-20260330031106-f09953afc57a | 2026-03-31 | < 0.0.0-20260330031106-f09953afc57a |
| CVE-2026-59832US | — | 0.46% (40th) | — | ✓0.0.0-20260704035520-68cc0f537dfa | 2026-07-09 | < 0.0.0-20260704035520-68cc0f537dfa |
| CVE-2026-31807US | medium6.1 | 0.46% (39th) | — | ✓0.0.0-20260310025236-297bd526708f | 2026-03-10 | < 0.0.0-20260310025236-297bd526708f |
| CVE-2026-74904US | —OT erhöht | 0.45% (39th) | — | ✓0.0.0-20260804015139-bd067a4fe9b2 | 2026-08-18 | < 0.0.0-20260804015139-bd067a4fe9b2 |
| CVE-2026-32749US | critical9.1 | 0.44% (38th) | — | ✗kein Fix | 2026-03-19 | 2 Versionen |
| CVE-2025-67488US | high8.8 | 0.44% (38th) | — | ✗kein Fix | 2025-12-09 | 2 Versionen |
| CVE-2026-72811US | — | 0.44% (38th) | — | ✓0.0.0-20260723004839-1a5b3431d5ab | 2026-08-14 | < 0.0.0-20260723004839-1a5b3431d5ab |
| CVE-2026-72798US | high8.6OT erhöht | 0.43% (38th) | — | ✓0.0.0-20260724121519-426991d155c0 | 2026-08-12 | < 0.0.0-20260724121519-426991d155c0 |