Recent vulnerabilities we're tracking. Click any CVE for the full profile, references, and our coverage.
| CVE | Severity | Fix | Vendor | Date | Covered |
|---|---|---|---|---|---|
| CVE-2026-49141 | high · 7.1 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-46484 | high · 8.1 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-40519 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11582 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-52778 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11557 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11393 | critical · 9 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11556 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11553 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-48507 | high · 7.1 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-46481 | high · 8.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-41448 | critical · 9.4 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-39910 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-25856 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-25855 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-25559 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-25555 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11531 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11530 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-48913 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-46657 | high · 7.1 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-46656 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-46440 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-44631 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-44185 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-42536 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-36786 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-34356 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-34355 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-34194 | high · 7.1 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-22164 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11528 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11524 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11523 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11522 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-36789 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11517 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-35429 | medium · 4.3 | ✓ FIX AVAILABLE | — | 2026-06-08 | — |
| CVE-2026-11577 | high · 7.2 | ✓ FIX AVAILABLE | — | 2026-06-08 | — |
| CVE-2026-50752 | high · 7.4 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-50751 | critical · 9.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11504 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11503 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11501 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-41724 | high · 8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-41723 | high · 8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-41722 | high · 8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-3238 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-08 | — |
| CVE-2026-11499 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11498 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11490 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11489 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11488 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11486 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11485 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11484 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11483 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11482 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2024-58349 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2024-58348 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2023-54352 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2023-54351 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2023-54350 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11474 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11472 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11471 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-08 | — |
| CVE-2026-11463 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11462 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11460 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-49494 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11457 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11456 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-7774 | ✓ FIX AVAILABLE | — | 2026-06-07 | — | |
| CVE-2026-3276 | ✓ FIX AVAILABLE | — | 2026-06-07 | — | |
| CVE-2026-8643 | medium · 5.5 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-5419 | low · 3.7 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-27145 | medium · 6.5 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-42507 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-10722 | low · 3.3 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-50219 | medium · 4.9 | ✓ FIX AVAILABLE | — | 2026-06-07 | — |
| CVE-2026-11452 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11451 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-11450 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-07 | — |
| CVE-2026-26422 | high · 8.4 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-11437 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-11435 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-11413 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-10725 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-9851 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-7537 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-8901 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-8438 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-9290 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-06 | — |
| CVE-2026-7654 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11416 | high · 8.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-36785 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11422 | high · 7.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-46493 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-45758 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45300 | high · 7.4 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11401 | high · 8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11400 | high · 8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-5415 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-5411 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-46392 | high · 8.7 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-46389 | critical · 10 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-10580 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-50733 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-49493 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-49492 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-45750 | critical · 9 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45749 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45748 | critical · 9.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45746 | critical · 9 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45745 | high · 8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45744 | critical · 9.9 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45743 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-45327 | high · 8.2 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-45291 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-45290 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-36500 | critical · 9.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11344 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11342 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2025-71318 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2025-71317 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2025-5088 | high · 8.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-9270 | critical · 9.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11362 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-6209 | critical · 9.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-6208 | critical · 9.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-6207 | critical · 9.1 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-48095 | high · 8.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11334 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-10879 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-50234 | high · 7.5 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-50232 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-50231 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-50264 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50261 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50260 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50259 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50258 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50257 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50256 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50265 | high · 7 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-21031 | high · 7.8 | ✓ FIX AVAILABLE | samsung | 2026-06-05 | — |
| CVE-2026-21030 | high · 7.8 | ✓ FIX AVAILABLE | samsung | 2026-06-05 | — |
| CVE-2026-21029 | high · 7.8 | ✓ FIX AVAILABLE | samsung | 2026-06-05 | — |
| CVE-2026-6274 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-49777 | critical · 10 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11332 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50593 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-7763 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-7762 | critical · 9.8 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-41567 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-11307 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11306 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11305 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11304 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11303 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11301 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11297 | high · 7.7 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11296 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11295 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11293 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11282 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11279 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11272 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11269 | high · 7.1 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11265 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11262 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11256 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11255 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11250 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-05 | — | |
| CVE-2026-11248 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11242 | high · 7.5 | ✓ FIX AVAILABLE | 2026-06-05 | — | |
| CVE-2026-11241 | high · 8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-11239 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-10877 | high · 7.3 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-10586 | high · 7.2 | ⌛ NO FIX YET | — | 2026-06-05 | — |
| CVE-2026-48579 | critical · 9.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-48567 | critical · 10 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-45497 | high · 7.7 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-20245 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11237 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11236 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11235 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11231 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11230 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11224 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11218 | medium · 6.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11213 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11211 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11207 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11202 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11201 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11198 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11191 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11188 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11185 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |