# CVE-2024-22031: Rancher users who can create Projects can gain access to arbitrary projects

> Users with project creation rights can escalate privileges to access arbitrary projects in other clusters by exploiting namespace naming collisions.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-8h6m-wv39-239m, GO-2025-3647

## What is CVE-2024-22031?

CVE-2024-22031 is a high-severity vulnerability in SUSE rancher, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-22031?

7 open source packages ship an affected version, including github.com/rancher/rancher.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rancher` | Go | All versions | None |
| `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.5 |
| `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.5 |
| `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.1 |
| `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.1 |
| `github.com/rancher/rancher` | Go | From 2.8.0 | 2.9.9 |
| `github.com/rancher/rancher` | Go | From 2.8.0 | 2.9.9 |

## How do I fix CVE-2024-22031?

Upgrade github.com/rancher/rancher to a fixed version for your release line: 2.10.5, 2.11.1 or 2.9.9.

## Is CVE-2024-22031 being exploited?

There is no known exploitation of CVE-2024-22031 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22031 and fix it if it is affected.

What it is: CVE-2024-22031 is a high-severity vulnerability in SUSE rancher, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22031 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rancher (Go): affected all versions; no fix listed
- github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.5
- github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.5
- github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.1
- github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.1
- github.com/rancher/rancher (Go): affected from 2.8.0; fixed in 2.9.9
- github.com/rancher/rancher (Go): affected from 2.8.0; fixed in 2.9.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22031/ (Markdown: https://insights.sbomify.com/CVE-2024-22031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22031
- OSV: https://osv.dev/vulnerability/CVE-2024-22031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22031/
Summaries are generated and may contain mistakes; the official description above is the record.