CVE-2024-22031 json
Rancher users who can create Projects can gain access to arbitrary projects
published last yr. modified 15d ago also GHSA-8h6m-wv39-239m , GO-2025-3647 , EUVD-2024-55800
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/rancher/rancher 2.9.9, 2.10.5, 2.11.1
- SUSE rancher 2.9.9, 2.10.5, 2.11.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250506T153719-1.1
opensuse advisories openSUSE-SU-2025:15059-1
Is CVE-2024-22031 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 28d ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/rancher/rancher | >=2.8.0, <2.9.9 >=2.10.0, <2.10.5 >=2.11.0, <2.11.1 all versions |
2.9.9 2.10.5 2.11.1 |
Affected products
- SUSE rancher
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/rancher/rancher/commit/7f16b596120dd382ce6e9ed0baf83bc23f633054
web
-
github.com
/rancher/rancher/commit/9c1d1c2bfcba36ae4f06c1fd043eb539ad801d4d
web
-
github.com
/rancher/rancher/commit/b0be28f86fc556414bd9b323f05b2b4bf8317c2d
web
-
github.com
/rancher/rancher/commit/f036e8b6ab726c3abbc03bbf7c8d0d53373c84e5
web
- bugzilla.suse.com /show_bug.cgi?id=CVE-2024-22031
-
github.com
/rancher/rancher/security/advisories/GHSA-8h6m-wv39-239m
web, advisory
-
github.com
/rancher/rancher
package
-
pkg.go.dev
/vuln/GO-2025-3647
web
Sources
- CVE List CVE-2024-22031
- GitHub Advisory GHSA-8h6m-wv39-239m
- NVD CVE-2024-22031
- OSV GO-2025-3647
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.