Recent vulnerabilities we're tracking. Click any CVE for the full profile, references, and our coverage.
| CVE | Severity | Fix | Vendor | Date | Covered |
|---|---|---|---|---|---|
| CVE-2026-40322 | critical · 9 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40318 | high · 8.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40259 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-41113 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40170 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6442 | high · 8.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-41082 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3324 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-37347 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-37345 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-37338 | critical · 9.4 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-37337 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-37336 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-33804 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-30656 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-30459 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6270 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-5785 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2025-64669 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-16 | — |
| CVE-2026-31843 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3489 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6284 | FIX STATUS UNKNOWN | — | 2026-04-16 | — | |
| CVE-2026-5387 | FIX STATUS UNKNOWN | — | 2026-04-16 | — | |
| CVE-2026-32648 | FIX STATUS UNKNOWN | — | 2026-04-16 | — | |
| CVE-2026-23772 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2024-2374 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2025-14868 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-41035 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3876 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-1620 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-5050 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3614 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3599 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-3596 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-22619 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2023-3634 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6351 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6350 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-6348 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-41015 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40504 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40960 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40959 | critical · 9.3 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40502 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-4880 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40245 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40193 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-04-16 | — |
| CVE-2026-40316 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-6388 | critical · 9.1 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-40261 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40176 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40173 | critical · 9.4 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-22676 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-6384 | high · 7.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6363 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6361 | high · 7.2 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6360 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6359 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6358 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6319 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6318 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6317 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6316 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6315 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6314 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6311 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6310 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6309 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6308 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6307 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6306 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6305 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6304 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6303 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6302 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6301 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6300 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6299 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6297 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-6296 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-35569 | high · 8.7 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2025-41118 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-4857 | high · 8.4 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-34632 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-34393 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-34242 | high · 7.7 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-33667 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-33435 | high · 8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-6290 | high · 8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30993 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-6372 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30996 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30995 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30994 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-20186 | critical · 9.9 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-20184 | critical · 9.8 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-20180 | critical · 9.9 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2026-20147 | critical · 9.9 | ✓ FIX AVAILABLE | — | 2026-04-15 | — |
| CVE-2025-63029 | high · 7.6 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30625 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30624 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30617 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30616 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30615 | high · 8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30461 | high · 8.3 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-20205 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-20204 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2025-67841 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30364 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2024-53412 | high · 8.4 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-4145 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-4134 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-0827 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40784 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40764 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40745 | high · 7.6 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40744 | high · 8.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-30778 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-33807 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2024-33618 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-5694 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-5617 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-3643 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-3461 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2025-40899 | high · 8.9 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2025-40897 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-33055 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-33056 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-2646 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-2645 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-3579 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-3849 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-3644 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-27171 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-27139 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2025-14523 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2025-61729 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-33671 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2025-1220 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-1519 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2025-30258 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5088 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-34480 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-34479 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-34481 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-35201 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-1502 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5446 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5392 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5263 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5460 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5772 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5447 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5778 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5188 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5295 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5264 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5503 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5479 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5477 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5448 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5507 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5501 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5194 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5504 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5500 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5393 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-5466 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-33555 | ✓ FIX AVAILABLE | — | 2026-04-15 | — | |
| CVE-2026-40719 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-5397 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40104 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40090 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-39971 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-39884 | high · 8.3 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-39842 | critical · 9.9 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-33806 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-2834 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-1555 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2025-54550 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-15 | — |
| CVE-2026-40688 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-39399 | critical · 9.6 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-39387 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-35589 | high · 8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-35031 | critical · 9.9 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-34457 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33023 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33021 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-27298 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27297 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27296 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27295 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27294 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27293 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27292 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27290 | high · 8.6 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-40291 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-35196 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-34631 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34619 | high · 7.7 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |