CVE Database
Tracked vulnerabilities — sorted by priority for IT practitioners.
1905
Critical
559
Exploited in Wild
559
CISA KEV
| CVE ID | Severity | Vendor | CVSS | KEV | Exploited | Patched | Published | Actions |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-18431 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 26, 2026 | |
| CVE-2026-19632 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 26, 2026 | |
| CVE-2026-80138 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-80104 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-65098 | CRITICAL | Nvidia | 9.8 | — | No | ✓ | August 25, 2026 | Patch |
| CVE-2026-65084 | CRITICAL | Nvidia | 9.8 | — | No | ✓ | August 25, 2026 | Patch |
| CVE-2026-65081 | CRITICAL | Nvidia | 9.8 | — | No | ✓ | August 25, 2026 | Patch |
| CVE-2026-79787 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-79675 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2024-58378 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2022-51000 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-16286 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-78570 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-78477 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-78676 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-56710 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-56705 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 25, 2026 | |
| CVE-2026-71921 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-71914 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-77915 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-76071 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-76070 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-78211 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-78168 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 24, 2026 | |
| CVE-2026-8445 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 23, 2026 | |
| CVE-2026-7808 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 23, 2026 | |
| CVE-2026-5388 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 23, 2026 | |
| CVE-2026-4703 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 22, 2026 | |
| CVE-2026-78003 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 22, 2026 | |
| CVE-2026-59318 | CRITICAL | Vmware | 9.8 | — | No | ✓ | August 21, 2026 | Patch |
| CVE-2026-77264 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 21, 2026 | |
| CVE-2026-72843 | CRITICAL | Vulncheck | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-19437 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-18832 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-17436 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-17160 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17157 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17152 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17145 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17142 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17141 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17138 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-17136 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17122 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17118 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17040 | CRITICAL | Unspecified | 9.8 | — | No | ✗ | August 20, 2026 | |
| CVE-2026-17024 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-17006 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-17000 | CRITICAL | IBM | 9.8 | — | No | ✓ | August 20, 2026 | Patch |
| CVE-2026-19586 | CRITICAL | TP Link | 9.8 | — | No | ✓ | August 20, 2026 | Patch |