cve.bz

CVE-2024-22031 suse rancher: Incorrect Authorization

8.5 highEPSS 0.4%Fix available

High (8.5) in suse rancher. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/rancher/rancher 2.10.5, 2.11.1, 2.9.9.

On this page
A vulnerability has been identified within Rancher where a user with the ability to create a project, on a certain cluster, can create a project with the same name as an existing project in a different cluster. This results in the user gaining access to the other project in the different cluster, resulting in a privilege escalation. This happens because the namespace used on the local cluster to store related resources (PRTBs and secrets) is the name of the project.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-22031 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-22031?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-22031?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-2024-22031 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
SUSE rancherfrom 2.8.0 before 2.9.9
SUSE rancherfrom 2.10.0 before 2.10.5
SUSE rancherfrom 2.11.0 before 2.11.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8h6m-wv39-239mGogithub.com/rancher/rancher>=2.8.0 <2.9.92.9.9
GHSA-8h6m-wv39-239mGogithub.com/rancher/rancher>=2.10.0 <2.10.52.10.5
GHSA-8h6m-wv39-239mGogithub.com/rancher/rancher>=2.11.0 <2.11.12.11.1
GO-2025-3647Gogithub.com/rancher/rancherall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedgovulncheck-vulndb0.0.20250506T153719-1.1openSUSE-SU-2025:15059-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

References

Check your stackJSON