CVE-2024-22031
8.5HighPublished 15 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-863
Impact
An authenticated user with project-creation permissions on one cluster can gain access to projects on other clusters. They only need standard network access and an account permitted to create projects.
Root cause
Rancher names the local cluster namespace holding ProjectRoleTemplateBindings and secrets after the project itself, causing resource collisions across clusters when project names match.
Affected systems
Versions not listed — check the vendor advisory.
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Fix & remediation
Check the vendor advisory (GHSA-8h6m-wv39-239m) for the patched release and upgrade Rancher; as an interim mitigation, restrict project creation permissions across clusters to trusted administrators only.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.