Recent vulnerabilities we're tracking. Click any CVE for the full profile, references, and our coverage.
| CVE | Severity | Fix | Vendor | Date | Covered |
|---|---|---|---|---|---|
| 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-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-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 | — |
| CVE-2026-34602 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33020 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33019 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33018 | high · 7 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-27306 | high · 8.4 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27305 | high · 8.6 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27304 | critical · 9.3 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27282 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34160 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-33715 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-27287 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-24893 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-40683 | high · 7.7 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-34630 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34618 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27313 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27312 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27311 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27310 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27289 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-5752 | critical · 9.3 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-34629 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34628 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34627 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34617 | high · 8.7 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34615 | critical · 9.3 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27303 | critical · 9.6 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27246 | critical · 9.3 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27245 | critical · 9.3 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27243 | critical · 9.3 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-34622 | high · 8.6 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27291 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27284 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27283 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-27238 | high · 7.8 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |
| CVE-2026-39815 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-39813 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-39808 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38532 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38530 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38529 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38528 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38527 | high · 8.5 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-38526 | critical · 9.9 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-23708 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-22828 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2025-65135 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2025-63939 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2025-61848 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-4369 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-4345 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-4344 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-04-14 | — |
| CVE-2026-27917 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27929 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32083 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32168 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27919 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32085 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32159 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27915 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27924 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32071 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32081 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32156 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32167 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26143 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26169 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27918 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27921 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32181 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32184 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27927 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32082 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32158 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32192 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32183 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32202 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32220 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33096 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33826 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32160 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32165 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32188 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33095 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33098 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26153 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26170 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33116 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26173 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27920 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32224 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32226 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26168 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26177 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26178 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26184 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32078 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32149 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32164 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32074 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32086 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32155 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32203 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33114 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32072 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32084 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32153 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32076 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32088 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32200 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-33101 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32198 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-32201 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26171 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-20930 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-23653 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26161 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-25250 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26162 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26166 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26183 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-25184 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26149 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26165 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26175 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26180 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-20945 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26151 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26155 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26174 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27906 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-23670 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26179 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-27908 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26154 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26167 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26160 | ✓ FIX AVAILABLE | — | 2026-04-14 | — | |
| CVE-2026-26181 | ✓ FIX AVAILABLE | — | 2026-04-14 | — |