SUSE Rancher up to 2.15.2 Shell improper authorization

Summaryinfo

A vulnerability identified as critical has been detected in SUSE Rancher up to 2.11.18/2.12.14/2.13.10/2.14.6/2.15.2. Affected by this issue is some unknown functionality of the component Shell. The manipulation leads to improper authorization. This vulnerability is documented as CVE-2026-104623. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in SUSE Rancher up to 2.11.18/2.12.14/2.13.10/2.14.6/2.15.2. This issue affects some unknown functionality of the component Shell. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-104623 since 10/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/30/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

Upgrading to version 2.11.19, 2.12.15, 2.13.11, 2.14.7 or 2.15.3 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• SUSE

Name

• Rancher

Version

• 2.11.0
• 2.11.1
• 2.11.2
• 2.11.3
• 2.11.4
• 2.11.5
• 2.11.6
• 2.11.7
• 2.11.8
• 2.11.9
• 2.11.10
• 2.11.11
• 2.11.12
• 2.11.13
• 2.11.14
• 2.11.15
• 2.11.16
• 2.11.17
• 2.11.18
• 2.12.0
• 2.12.1
• 2.12.2
• 2.12.3
• 2.12.4
• 2.12.5
• 2.12.6
• 2.12.7
• 2.12.8
• 2.12.9
• 2.12.10
• 2.12.11
• 2.12.12
• 2.12.13
• 2.12.14
• 2.13.0
• 2.13.1
• 2.13.2
• 2.13.3
• 2.13.4
• 2.13.5
• 2.13.6
• 2.13.7
• 2.13.8
• 2.13.9
• 2.13.10
• 2.14.0
• 2.14.1
• 2.14.2
• 2.14.3
• 2.14.4
• 2.14.5
• 2.14.6
• 2.15.0
• 2.15.1
• 2.15.2

License

• open-source

Website

• Vendor: https://www.suse.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion