CVE-2024-22031
Received Received - Intake

Privilege Escalation in Rancher via Project Name Clash

Publication date: 2026-10-15

Last updated on: 2026-10-15

Assigner: SUSE

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-15
Generated
2026-10-15
AI Q&A
2026-10-15
EPSS Evaluated
N/A
NVD
CVE-2024-22031
EUVD
EUVD-2024-55800

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
SUSE rancher 2.8.0
SUSE rancher 2.10.0
SUSE rancher 2.11.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Rancher allows a user with project creation privileges on a cluster to create a project with the same name as an existing project in a different cluster. This leads to unauthorized access to the other project, causing a privilege escalation. The issue occurs because Rancher uses the project name as the namespace for related resources, which can cause namespace collisions across clusters.

Detection Guidance

To detect this vulnerability, administrators can check for duplicate project names across clusters. Use Rancher's API or UI to list all projects and compare names. If duplicates exist, they may indicate potential namespace collisions. The vulnerability occurs because Rancher uses project names as namespaces for resources like PRTBs and secrets.

Impact Analysis

This vulnerability can allow unauthorized users to gain access to sensitive projects and their resources in other clusters. This may lead to data breaches, unauthorized modifications, or disruptions in service, depending on the permissions of the accessed project.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating compliance requirements such as GDPR or HIPAA. Unauthorized access may result in data leaks or improper handling of protected information, leading to legal and regulatory penalties.

Mitigation Strategies

Immediately upgrade Rancher to versions 2.9.9, 2.10.5, or 2.11.1 or later to apply the patch. If upgrading is not possible, ensure no duplicate project names exist across clusters. Delete and recreate any affected projects to prevent namespace collisions. The fix introduces a new `backingNamespace` field to replace project names for namespace generation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2024-22031. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart