Recent vulnerabilities we're tracking. Click any CVE for the full profile, references, and our coverage.
| CVE | Severity | Fix | Vendor | Date | Covered |
|---|---|---|---|---|---|
| CVE-2026-26422 | high · 8.4 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-11437 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-11435 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-11413 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-9851 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-7537 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-8901 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-8438 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-9290 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-06 | — |
| CVE-2026-7654 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11416 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11422 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-46493 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45758 | critical · 9.6 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45300 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11401 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11400 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-5415 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-5411 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-46392 | high · 8.7 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-46389 | critical · 10 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-10580 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-50733 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-49493 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-49492 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45750 | critical · 9 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45749 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45748 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45746 | critical · 9 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45745 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45744 | critical · 9.9 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45743 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45327 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45291 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-45290 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11344 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11342 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2025-71318 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2025-71317 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2025-5088 | high · 8.3 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-6209 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-6208 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-6207 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-48095 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11334 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-50234 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-50232 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-50231 | high · 7.2 | FIX STATUS UNKNOWN | — | 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 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-49777 | critical · 10 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-11332 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-05 | — |
| CVE-2026-50593 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-7763 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-7762 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-41567 | high · 7.2 | FIX STATUS UNKNOWN | — | 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 | FIX STATUS UNKNOWN | — | 2026-06-05 | — |
| CVE-2026-10586 | high · 7.2 | FIX STATUS UNKNOWN | — | 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.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11218 | high · 8.1 | ✓ 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 | — |
| CVE-2026-11179 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11177 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11175 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11173 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11172 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11171 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11170 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11169 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11167 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11165 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11164 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11163 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11158 | high · 8.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11154 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11153 | critical · 9.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11152 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11151 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11149 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11147 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11146 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11144 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11136 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11131 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11130 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11125 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11120 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11119 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11118 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11117 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11116 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11115 | high · 7.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11114 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11113 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11112 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11111 | high · 8.1 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11108 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11103 | high · 7.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11102 | high · 8.8 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11100 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11095 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11094 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11092 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11091 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11088 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11086 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11085 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11082 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11080 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11079 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11077 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11076 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11074 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11072 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11071 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11070 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11068 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11066 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11065 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11063 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11061 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11060 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11059 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11058 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11056 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11055 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11054 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11052 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11050 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11049 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11047 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11046 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11043 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11042 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11041 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11040 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11037 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11035 | high · 7.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11030 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11028 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11012 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11010 | high · 8.3 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11009 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11003 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-11002 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-11000 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-10995 | high · 8.8 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-10991 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |
| CVE-2026-10990 | critical · 9.6 | ✓ FIX AVAILABLE | 2026-06-04 | — | |
| CVE-2026-10989 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-04 | — |