CVE-2024-22031 — Rancher users who can create Projects can gain access to arbitrary projects
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Go Github.com/rancher/rancher: fixed in version 2.9.9 — github.com (GitHub Security Advisories)
- Go Github.com/rancher/rancher: fixed in version 2.10.5 — github.com (GitHub Security Advisories)
- Go Github.com/rancher/rancher: fixed in version 2.11.1 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (SUSE Rancher, Go Github.com/rancher/rancher).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| SUSE | Rancher | ≥ 2.8.0 and < 2.9.9≥ 2.10.0 and < 2.10.5≥ 2.11.0 and < 2.11.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Go | Github.com/rancher/rancher | ≥ 2.8.0 and < 2.9.9≥ 2.10.0 and < 2.10.5≥ 2.11.0 and < 2.11.1 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.5 | CVSS 3.1 | High | 1.8 | 6.0 | meissner@suse.de via NIST National Vulnerability Database |
| 8.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.5 | CVSS 3.1 | High | — | — | suse via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: meissner@suse.de) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Fix documented
- Affected products added · go/github.com/rancher/rancher
- Affected products added · suse/rancher
- Record published
- CVSS changed · 8.5
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- github.com/rancher/rancher/commit/9c1d1c2bfcba36ae4f06c1fd043eb539ad801d4d
- github.com/rancher/rancher/commit/f036e8b6ab726c3abbc03bbf7c8d0d53373c84e5
- bugzilla.suse.com/show_bug.cgi
- github.com/rancher/rancher/commit/b0be28f86fc556414bd9b323f05b2b4bf8317c2d
- github.com/rancher/rancher/commit/7f16b596120dd382ce6e9ed0baf83bc23f633054
- github.com/advisories/GHSA-8h6m-wv39-239m
- pkg.go.dev/vuln/GO-2025-3647
- github.com/rancher/rancher/security/advisories/GHSA-8h6m-wv39-239m
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-88808 Fleet agent copies downstream resources with cluster-admin privileges, allowing cross-namespace writes on downstream clusters 17d
- Medium CVE-2026-93539 Unauthenticated GitRepo Spec Mutation via Fleet Git Webhook Receiver 17d
- Medium CVE-2026-93540 Fleet applies namespace labels and annotations without the bundle's service account privileges 17d
- High CVE-2026-93538 Cross-tenant BundleDeployment and Secret disclosure via spoofed cluster labels during agent-initiated registration in Fleet 17d
- Medium CVE-2026-93537 Path traversal in Fleet Helm valuesFiles allows disclosure of files outside the bundle directory 17d
- Medium CVE-2026-44948 Path Traversal in Rancher Fleet ImageScan GitRepo Path Handler Jun 30, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-22031 is "Rancher users who can create Projects can gain access to arbitrary projects", rated High. It affects Rancher (SUSE); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.