All vulnerabilities
CVE-2024-22031GHSA-8h6m-wv39-239mGO-2025-3647

Rancher users who can create Projects can gain access to arbitrary projects

SUSE rancherGoApplications & CMS
Open in ThreatlineRecord JSON
CVSS
8.5High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.43%Chance of exploitation activity in the next 30 days, higher than 36% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in2.9.9Also 2.10.5, 2.11.1CVE List
Published15 Oct 2026Updated 16 Oct 2026CVE List

What fixes it

  • 2.9.9rancherCVE List
  • 2.10.5rancherCVE List
  • 2.11.1rancherCVE List
  • 2.9.9github.com/rancher/rancher, GoOSVgo get github.com/rancher/rancher@v2.9.9
  • 2.10.5github.com/rancher/rancher, GoOSVgo get github.com/rancher/rancher@v2.10.5
  • 2.11.1github.com/rancher/rancher, GoOSVgo get github.com/rancher/rancher@v2.11.1

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 6

  • rancheraffected: 2.8.0 before 2.9.9CVE List
  • rancheraffected: 2.10.0 before 2.10.5CVE List
  • rancheraffected: 2.11.0 before 2.11.1CVE List
  • github.com/rancher/rancher, Gofrom 2.8.0, fixed in 2.9.9OSV
  • github.com/rancher/rancher, Gofrom 2.10.0, fixed in 2.10.5OSV
  • github.com/rancher/rancher, Gofrom 2.11.0, fixed in 2.11.1OSV

References 2