Rancher vulnerabilities: known CVEs & security history
SUSE · Virtualization · 8 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Rancher release lines — 8 in total. A CVE here doesn't mean your version is affected — check Rancher's current status and the safe version to run.
Known Rancher CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-41053 | high | 8.8 | 0% | 2026 |
| CVE-2026-41052 | high | 8.8 | 0% | 2026 |
| CVE-2026-71404 | high | 8.7 | 0% | 2026 |
| CVE-2026-75035 | high | 7.7 | 0% | 2026 |
| CVE-2026-75033 | high | 7.7 | 0% | 2026 |
| CVE-2026-75034 | high | 7.4 | 0% | 2026 |
| CVE-2026-44946 | high | 7.4 | 0% | 2026 |
| CVE-2026-71403 | medium | 6.1 | 0% | 2026 |
Is my Rancher 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 Rancher version → · Monitor Rancher for new CVEs →
Rancher vulnerabilities — frequently asked
How many known vulnerabilities does Rancher have?
IsItPatched tracks 8 CVEs for Rancher. 0 are critical-severity and 7 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Rancher have any actively-exploited vulnerabilities?
None of Rancher's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Rancher vulnerability?
Among tracked issues, CVE-2026-41053 (HIGH, CVSS 8.8) ranks highest — a CWE-303 weakness.
Is Rancher safe to use?
It depends on the version. The latest supported Rancher release (2.15.1) 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: Rancher security status · Rancher end-of-life · actively-exploited CVEs. Always verify against SUSE's advisories — see our disclaimer.