| 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-96951US | high8.8OT critical | 9.81% (96th) | KEV | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-85884US | high7.8OT elevated | 0.45% (39th) | Exploit | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83834US | high7.0 | 0.30% (22nd) | Exploit | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-88091US | high7.8 | 2.93% (87th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-96186US | high7.8 | 2.40% (84th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-105016US | critical9.8 | 1.66% (76th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-88159US | high8.8 | 1.44% (73rd) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83655US | high7.5 | 1.36% (71st) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83516US | high7.5 | 1.36% (71st) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83855US | high7.5 | 1.33% (71st) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-105723US | critical9.8 | 1.30% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83843US | high7.5 | 1.30% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83795US | high7.5 | 1.30% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70133US | high7.5 | 1.30% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83647US | high7.5 | 1.30% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83685US | medium6.5 | 1.29% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83683US | medium6.5 | 1.28% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83860US | high7.5 | 1.27% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70031US | high7.5 | 1.27% (70th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-102217US | high8.8 | 1.26% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70163US | high7.5 | 1.25% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70170US | medium6.5 | 1.23% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83649US | medium6.5 | 1.23% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70072US | medium6.5 | 1.23% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83667US | medium6.5 | 1.23% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83648US | medium6.5 | 1.23% (69th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-103569US | high7.5 | 1.14% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83770US | critical9.8 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83693US | critical9.8 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83521US | medium6.5 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-87716US | high7.5 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-85808US | high7.5 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-84017US | high7.5 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83677US | high7.5 | 1.13% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-100219US | critical9.8 | 1.10% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-100202US | critical9.8 | 1.10% (66th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70153US | critical9.8 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70147US | critical9.8 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-97814US | critical9.8 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83670US | high7.5 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83578US | critical9.8 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70096US | critical9.8 | 1.09% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83910US | critical9.8 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83519US | critical9.8 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83517US | critical9.8 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-70157US | critical9.8 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-83784US | high8.8 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-97819US | medium6.5 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-97817US | medium6.5 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
| CVE-2026-97813US | medium6.5 | 1.08% (65th) | — | ✓10.0.26300.9711 | 2026-10-13 | 2 versions |
showing 50 of 1,007