| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2026-33824US | —OT critical | 77.1% (100th) | KEV | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-81963US | high7.8OT critical | 0.39% (33rd) | KEV | ✓10.0.28000.2954 | 2026-09-08 | < 10.0.28000.2954 |
| CVE-2026-68820US | —OT critical | 0.33% (26th) | KEV | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-96951US | high8.8OT critical | 9.81% (96th) | KEV | ✓10.0.28000.3231 | 2026-10-13 | < 10.0.28000.3231 |
| CVE-2026-49160US | — | 56.6% (99th) | Exploit | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-42980US | — | 6.95% (94th) | Exploit | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-50507US | —OT elevated | 5.02% (92nd) | Exploit | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-24294US | — | 4.85% (92nd) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-40369US | — | 4.72% (92nd) | Exploit | ✓10.0.28000.2113 | 2026-05-12 | < 10.0.28000.2113 |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-24291US | — | 3.30% (88th) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-41096US | — | 2.70% (86th) | Exploit | ✓10.0.28000.2113 | 2026-05-12 | < 10.0.28000.2113 |
| CVE-2026-45585US | — | 1.89% (79th) | Exploit | ✗no fix | 2026-05-20 | — |
| CVE-2026-25177US | — | 1.33% (71st) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-34348US | — | 1.00% (62nd) | Exploit | ✓10.0.28000.2269 | 2026-07-14 | < 10.0.28000.2269 |
| CVE-2026-56190US | — | 0.97% (62nd) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | < 10.0.28000.2525 |
| CVE-2026-49179US | — | 0.86% (58th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-33827US | — | 0.84% (58th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-50369US | — | 0.70% (53rd) | Exploit | ✓10.0.28000.2269 | 2026-07-14 | 2 versions |
| CVE-2026-26128US | — | 0.65% (51st) | Exploit | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-69451US | high7.1 | 0.57% (47th) | Exploit | ✓10.0.28000.2954 | 2026-09-08 | < 10.0.28000.2954 |
| CVE-2026-32223US | — | 0.52% (44th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-54984US | — | 0.47% (40th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-50416US | low3.3 | 0.46% (40th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | < 10.0.28000.2525 |
| CVE-2026-69328US | high7.8 | 0.46% (39th) | Exploit | ✓10.0.28000.2954 | 2026-09-08 | < 10.0.28000.2954 |
| CVE-2026-26179US | — | 0.44% (38th) | Exploit | ✓10.0.28000.1836 | 2026-04-14 | < 10.0.28000.1836 |
| CVE-2026-97798US | high7.8 | 0.37% (31st) | Exploit | ✓10.0.28000.3231 | 2026-10-13 | < 10.0.28000.3231 |
| CVE-2026-54992US | high7.8 | 0.34% (27th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | < 10.0.28000.2525 |
| CVE-2026-62737US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-62735US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-50402US | — | 0.33% (27th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | 2 versions |
| CVE-2026-49176US | — | 0.33% (26th) | Exploit | ✓10.0.28000.2269 | 2026-07-14 | 2 versions |
| CVE-2026-58635US | — | 0.32% (25th) | Exploit | ✓10.0.28000.2269 | 2026-07-14 | 2 versions |
| CVE-2026-34344US | — | 0.31% (24th) | Exploit | ✓10.0.28000.2113 | 2026-05-12 | < 10.0.28000.2113 |
| CVE-2026-83991US | medium5.5OT elevated | 0.30% (23rd) | Exploit | ✓10.0.28000.2954 | 2026-09-08 | < 10.0.28000.2954 |
| CVE-2026-83834US | high7.0 | 0.30% (22nd) | Exploit | ✓10.0.28000.3231 | 2026-10-13 | < 10.0.28000.3231 |
| CVE-2026-66804US | — | 0.30% (22nd) | Exploit | ✓10.0.28000.2704 | 2026-08-11 | < 10.0.28000.2704 |
| CVE-2026-50343US | — | 0.30% (22nd) | Exploit | ✓10.0.28000.2269 | 2026-07-14 | 2 versions |
| CVE-2026-42978US | — | 0.25% (16th) | Exploit | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-54107US | high7.0 | 0.21% (12th) | Exploit | ✓10.0.28000.2525 | 2026-07-14 | < 10.0.28000.2525 |
| CVE-2026-47291US | — | 25.3% (98th) | — | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-45657US | — | 15.5% (97th) | — | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-24289US | — | 4.59% (92nd) | — | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-45586US | — | 3.63% (89th) | — | ✓10.0.28000.2269 | 2026-06-09 | < 10.0.28000.2269 |
| CVE-2026-50509US | — | 3.53% (89th) | — | ✓10.0.28000.2525 | 2026-07-14 | < 10.0.28000.2525 |
| CVE-2026-25187US | — | 3.23% (88th) | — | ✓10.0.28000.1719 | 2026-03-10 | < 10.0.28000.1719 |
| CVE-2026-88091US | high7.8 | 2.93% (87th) | — | ✓10.0.28000.3231 | 2026-10-13 | < 10.0.28000.3231 |
| CVE-2026-69694US | high7.0 | 2.80% (86th) | — | ✓10.0.28000.2954 | 2026-09-08 | < 10.0.28000.2954 |
| CVE-2026-40398US | — | 2.67% (86th) | — | ✓10.0.28000.2113 | 2026-05-12 | < 10.0.28000.2113 |
showing 50 of 2,081