Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Rancher versions from 2.8.0 before 2.9.9, from 2.10.0 before 2.10.5, and from 2.11.0 before 2.11.1 are affected. A user who is allowed to create projects on one cluster can create a project with the same name as a project on another cluster and gain access to that project, which is a privilege escalation. Upgrade to 2.9.9, 2.10.5, or 2.11.1. The 2.8 release line has no fix; the advisory's workaround is to prevent users from creating projects with names already used in other clusters.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.5 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H | CNA (suse) |
- CISA KEV Not listed.
- EPSS 0.0043, the 38th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8h6m-wv39-239m
- OSV: GHSA-8h6m-wv39-239m
- github.com/rancher/rancher/security/advisories/GHSA-8h6m-wv39-239m
- github.com/rancher/rancher/commit/7f16b596120dd382ce6e9ed0baf83bc23f633054
- github.com/rancher/rancher/commit/9c1d1c2bfcba36ae4f06c1fd043eb539ad801d4d
- github.com/rancher/rancher/commit/b0be28f86fc556414bd9b323f05b2b4bf8317c2d
- github.com/rancher/rancher/commit/f036e8b6ab726c3abbc03bbf7c8d0d53373c84e5
- github.com/rancher/rancher
- pkg.go.dev/vuln/GO-2025-3647