Recent vulnerabilities we're tracking. Click any CVE for the full profile, references, and our coverage.
| CVE | Severity | Fix | Vendor | Date | Covered |
|---|---|---|---|---|---|
| CVE-2026-10777 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-10771 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-50033 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-44682 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-44609 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-42061 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-40290 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36611 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36609 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36608 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36607 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36606 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-20230 | high · 8.6 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2026-37462 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36748 | critical · 9 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-36576 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-5241 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2022-49042 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2022-49036 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35085 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35084 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35083 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35082 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35081 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35080 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35079 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35078 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35077 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35076 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-35075 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-47065 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-41032 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-15656 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-15655 | high · 7.6 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-14774 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-14773 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-14772 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-14771 | critical · 9.9 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-4035 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2025-15654 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-44777 | medium · 5.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-13462 | ✓ FIX AVAILABLE | — | 2026-06-03 | — | |
| CVE-2026-4224 | ✓ FIX AVAILABLE | — | 2026-06-03 | — | |
| CVE-2026-27142 | medium · 6.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2026-3713 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2026-2297 | ✓ FIX AVAILABLE | — | 2026-06-03 | — | |
| CVE-2025-58160 | ✓ FIX AVAILABLE | — | 2026-06-03 | — | |
| CVE-2025-61727 | medium · 6.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-60876 | medium · 6.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-61725 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-58188 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-61724 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-58186 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-58183 | medium · 4.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-55554 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-55551 | high · 7.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2024-58266 | low · 3.2 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-5791 | high · 7.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-4574 | medium · 6.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-46327 | low · 3.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-46394 | low · 3.2 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2024-58251 | low · 2.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-29923 | low · 3.7 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2024-7598 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-1180 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-1150 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-1151 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2025-1152 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2024-30896 | critical · 9.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2019-11254 | medium · 6.5 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2013-1633 | medium · 6.8 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2023-1386 | low · 3.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2023-27043 | medium · 5.3 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2020-8561 | medium · 4.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2021-25740 | low · 3.1 | ✓ FIX AVAILABLE | — | 2026-06-03 | — |
| CVE-2026-50031 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-10704 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-9516 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-9334 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2026-10694 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-03 | — |
| CVE-2010-0249 · KEV | high · 8.8 | ✓ FIX AVAILABLE | Microsoft | 2026-06-03 | — |
| CVE-2026-42504 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-35482 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-32625 | critical · 9.6 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-31942 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2024-14036 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2022-4992 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2021-4481 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2021-4480 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-49448 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-49443 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-49143 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-47201 | high · 8.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42849 | critical · 9.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10620 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10619 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-8036 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-8035 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-5076 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-5073 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-49120 | high · 8.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42342 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42211 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-38967 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-34077 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-33245 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-28299 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-1829 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10701 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10617 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10608 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10607 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-64390 | high · 7.4 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2021-4478 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2019-25722 | high · 7.6 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42074 | critical · 9.8 | ✓ FIX AVAILABLE | gitlawb | 2026-06-02 | — |
| CVE-2026-40715 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-24237 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-24221 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10606 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-0611 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-47117 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-45686 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-45685 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-45678 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-45553 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42654 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-40780 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-40619 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-30652 | high · 8.8 | FIX STATUS UNKNOWN | vivotek | 2026-06-02 | — |
| CVE-2026-30650 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-30649 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10629 | critical · 9.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10591 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-7313 | high · 8.7 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-7312 | critical · 10 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-7201 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-7198 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-7195 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-39555 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-39553 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-39552 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10622 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-10621 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-69369 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-68886 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-58897 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-58707 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2019-25719 | high · 8.6 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42685 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42684 | critical · 9.3 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42670 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-42669 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-39551 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-39550 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-58705 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-58024 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-53440 | high · 8.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-5422 | high · 8.1 | FIX STATUS UNKNOWN | jupyter | 2026-06-02 | — |
| CVE-2025-53345 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-53209 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2025-52759 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-3514 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-1784 | high · 8.8 | ✓ FIX AVAILABLE | — | 2026-06-02 | — |
| CVE-2026-6324 | medium · 4.8 | ✓ FIX AVAILABLE | — | 2026-06-02 | — |
| CVE-2026-10028 | medium · 4.3 | ✓ FIX AVAILABLE | — | 2026-06-02 | — |
| CVE-2026-8293 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2026-8206 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-02 | — |
| CVE-2022-0492 · KEV | high · 7.8 | ✓ FIX AVAILABLE | Linux | 2026-06-02 | — |
| CVE-2026-25879 | critical · 9.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-25277 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-25276 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-25260 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-25259 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-25258 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24782 | high · 7.6 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24752 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24092 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24091 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24090 | high · 7.1 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24089 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24088 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24087 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-24085 | high · 7.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2025-59606 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2025-59605 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2025-59604 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2019-25718 | high · 8.4 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-49491 | high · 8.2 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-40965 | critical · 10 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-40964 | high · 7.5 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-28580 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-28577 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-10293 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-10292 | high · 8.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-10290 | high · 7.3 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-0100 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-0099 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-0098 | high · 7.8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |
| CVE-2026-0097 | high · 8 | FIX STATUS UNKNOWN | — | 2026-06-01 | — |