Red Hat OpenShift vulnerabilities: known CVEs & security history
Red Hat · Infrastructure · 126 tracked CVEs · 2 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Red Hat OpenShift release lines — 126 in total, with 2 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Red Hat OpenShift's current status and the safe version to run.
Known Red Hat OpenShift CVEs
Actively-exploited and most-severe first. Showing the top 80 of 126. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-31431⚡ exploited | high | 7.8 | 100% | 2026 |
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2018-14721 | critical | 10 | 10% | 2019 |
| CVE-2019-14892 | critical | 9.8 | 6% | 2020 |
| CVE-2019-14379 | critical | 9.8 | 8% | 2019 |
| CVE-2018-11307 | critical | 9.8 | 6% | 2019 |
| CVE-2019-9636 | critical | 9.8 | 8% | 2019 |
| CVE-2018-19362 | critical | 9.8 | 11% | 2019 |
| CVE-2018-19361 | critical | 9.8 | 11% | 2019 |
| CVE-2018-19360 | critical | 9.8 | 11% | 2019 |
| CVE-2018-14720 | critical | 9.8 | 8% | 2019 |
| CVE-2018-14719 | critical | 9.8 | 10% | 2019 |
| CVE-2018-14718 | critical | 9.8 | 13% | 2019 |
| CVE-2017-7525 | critical | 9.8 | 38% | 2018 |
| CVE-2017-15095 | critical | 9.8 | 8% | 2018 |
| CVE-2026-4408 | critical | 9 | 3% | 2026 |
| CVE-2026-4480 | critical | 9 | 14% | 2026 |
| CVE-2026-54099 | high | 8.8 | 0% | 2026 |
| CVE-2026-1784 | high | 8.8 | 0% | 2026 |
| CVE-2026-54100 | high | 8.3 | 0% | 2026 |
| CVE-2026-0966 | high | 8.2 | 1% | 2026 |
| CVE-2024-6387 | high | 8.1 | 100% | 2024 |
| CVE-2024-5154 | high | 8.1 | 1% | 2024 |
| CVE-2024-1132 | high | 8.1 | 2% | 2024 |
| CVE-2023-4853 | high | 8.1 | 1% | 2023 |
| CVE-2018-5968 | high | 8.1 | 7% | 2018 |
| CVE-2026-3012 | high | 8 | 0% | 2026 |
| CVE-2026-48864 | high | 7.8 | 0% | 2026 |
| CVE-2026-6846 | high | 7.8 | 0% | 2026 |
| CVE-2025-5914 | high | 7.8 | 0% | 2025 |
| CVE-2025-0678 | high | 7.8 | 0% | 2025 |
| CVE-2024-45782 | high | 7.8 | 0% | 2025 |
| CVE-2024-9675 | high | 7.8 | 0% | 2024 |
| CVE-2020-1712 | high | 7.8 | 0% | 2020 |
| CVE-2026-42965 | high | 7.7 | 0% | 2026 |
| CVE-2025-13601 | high | 7.7 | 0% | 2025 |
| CVE-2023-6563 | high | 7.7 | 1% | 2023 |
| CVE-2026-42009 | high | 7.5 | 1% | 2026 |
| CVE-2026-33845 | high | 7.5 | 2% | 2026 |
| CVE-2026-5121 | high | 7.5 | 1% | 2026 |
| CVE-2026-4424 | high | 7.5 | 1% | 2026 |
| CVE-2025-7424 | high | 7.5 | 1% | 2025 |
| CVE-2025-6021 | high | 7.5 | 1% | 2025 |
| CVE-2024-12085 | high | 7.5 | 9% | 2025 |
| CVE-2024-1635 | high | 7.5 | 5% | 2024 |
| CVE-2018-12023 | high | 7.5 | 9% | 2019 |
| CVE-2018-12022 | high | 7.5 | 7% | 2019 |
| CVE-2018-12115 | high | 7.5 | 8% | 2018 |
| CVE-2026-46579 | high | 7.4 | 0% | 2026 |
| CVE-2026-71226 | high | 7.3 | 0% | 2026 |
| CVE-2026-1933 | high | 7.1 | 1% | 2026 |
| CVE-2026-42010 | high | 7.1 | 1% | 2026 |
| CVE-2023-6291 | high | 7.1 | 1% | 2024 |
| CVE-2026-44495 | high | 7 | 1% | 2026 |
| CVE-2026-104048 | medium | 6.8 | 0% | 2026 |
| CVE-2026-13595 | medium | 6.8 | 0% | 2026 |
| CVE-2025-26465 | medium | 6.8 | 8% | 2025 |
| CVE-2026-4878 | medium | 6.7 | 0% | 2026 |
| CVE-2025-7519 | medium | 6.7 | 0% | 2025 |
| CVE-2025-5915 | medium | 6.6 | 0% | 2025 |
| CVE-2026-71225 | medium | 6.5 | 0% | 2026 |
| CVE-2026-2340 | medium | 6.5 | 1% | 2026 |
| CVE-2026-9149 | medium | 6.5 | 0% | 2026 |
| CVE-2026-9150 | medium | 6.5 | 0% | 2026 |
| CVE-2026-3833 | medium | 6.5 | 1% | 2026 |
| CVE-2026-6732 | medium | 6.5 | 1% | 2026 |
| CVE-2026-39979 | medium | 6.5 | 1% | 2026 |
| CVE-2026-4426 | medium | 6.5 | 0% | 2026 |
| CVE-2025-12801 | medium | 6.5 | 0% | 2026 |
| CVE-2025-32990 | medium | 6.5 | 1% | 2025 |
| CVE-2025-32988 | medium | 6.5 | 1% | 2025 |
| CVE-2025-5351 | medium | 6.5 | 1% | 2025 |
| CVE-2024-12088 | medium | 6.5 | 5% | 2025 |
| CVE-2026-0964 | medium | 6.3 | 0% | 2026 |
| CVE-2026-104046 | medium | 6.2 | 0% | 2026 |
| CVE-2026-13757 | medium | 6.2 | 0% | 2026 |
| CVE-2026-4647 | medium | 6.1 | 0% | 2026 |
| CVE-2026-3442 | medium | 6.1 | 0% | 2026 |
| CVE-2026-3441 | medium | 6.1 | 0% | 2026 |
| CVE-2024-12086 | medium | 6.1 | 2% | 2025 |
46 older / lower-severity CVEs not shown — see Red Hat OpenShift's full record.
Is my Red Hat OpenShift version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Red Hat OpenShift version → · Monitor Red Hat OpenShift for new CVEs →
Red Hat OpenShift vulnerabilities — frequently asked
How many known vulnerabilities does Red Hat OpenShift have?
IsItPatched tracks 126 CVEs for Red Hat OpenShift, 2 of which are actively exploited (CISA KEV). 15 are critical-severity and 39 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Red Hat OpenShift have any actively-exploited vulnerabilities?
Yes — 2 Red Hat OpenShift CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. Patch these as a priority.
What is the most severe Red Hat OpenShift vulnerability?
Among tracked issues, CVE-2026-31431 (HIGH, CVSS 7.8), which is actively exploited, ranks highest — a CWE-669 weakness.
Is Red Hat OpenShift safe to use?
It depends on the version. The latest supported Red Hat OpenShift release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Red Hat OpenShift security status · Red Hat OpenShift end-of-life · actively-exploited CVEs. Always verify against Red Hat's advisories — see our disclaimer.