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.
Severity
CVSS 3.1
6.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3%(unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-104623 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104623?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104623?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104623 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
googlesky/CVE-2026-104623Harbor Check: matches CVE0 stars, Python, created PoC and Docker lab for CVE-2026-104623 — SUSE Rancher Manager local-cluster-shell authorization bypass: any authenticated user spawns a she…
Attack patterns (CAPEC)
CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High