Authorization bypass on the local cluster shell endpoint allows an unauthorized Rancher user to obtain a shell pod on the management cluster
Affects Rancher Manager 2.11.0 through 2.15.3 on the local cluster shell endpoint. Fixed in 2.15.3, 2.14.7, 2.13.11, 2.12.15 and 2.11.19.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.15.3, 2.14.7, 2.13.11, 2.12.15, 2.11.19
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SUSE Rancher Manager (versions 2.11 through 2.15 and possibly older) is affected in its local management cluster shell feature. An authenticated Rancher user without proper permission could bypass the authorization check and get a shell pod running on the management cluster.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A security vulnerability exists in the authorization handling for the local (management) cluster shell feature of SUSE Rancher Manager 2.15.0 up to 2.15.3, 2.14.0 up to 2.14.7, 2.13.0 up to 2.13.11, 2.12.0 up to 2.12.15, 2.11.0 up to 2.11.19 and possible older versions. The authorization check that was introduced to protect this feature was not applied to every API route that can reach it, so an alternative request form reached the shell handler without the access check being evaluated. This could allow any authenticated users to run a pod on the management cluster.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Rancher
From 2.15.0 · fixed in 2.15.3; From 2.14.0 · fixed in 2.14.7; From 2.13.0 · fixed in 2.13.11; From 2.12.0 · fixed in 2.12.15; From 2.11.0 · fixed in 2.11.19
References 2
GitHub · rancher/rancher
GitHub · googlesky/CVE-2026-104623
Questions about CVE-2026-104623
What does this mean?
An authenticated Rancher user who lacks authorization can obtain an interactive shell pod on the management cluster in the cattle-system namespace. That pod gives compute resources and a network position inside the management plane.Source: github.com
Am I affected, and how do I check?
Rancher Manager versions from 2.11.0 through 2.15.3 fall in the affected ranges, per the advisory's affected versions. Check the installed Rancher Manager version against those ranges.Source: github.com
What should I do about it?
Upgrade to the fixed release for the branch in use: 2.15.3, 2.14.7, 2.13.11, 2.12.15 or 2.11.19.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data