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

Advisory record · `GHSA-8h6m-wv39-239m`

- **Identifiers:** `GHSA-8h6m-wv39-239m` · `CVE-2024-22031` · `GO-2025-3647`
- **State:** Confirmed
- **Severity:** CVSS 8.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 25 Apr 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Apr 2025, 15:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/rancher/rancher` (Go): affected `>=2.8.0, <2.9.9 || >=2.10.0, <2.10.5 || >=2.11.0, <2.11.1`; fixed in `2.9.9`, `2.10.5`, `2.11.1`

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

Written 1 Nov 2026.

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

- 8.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`, from 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](https://osv.dev/vulnerability/GHSA-8h6m-wv39-239m)

## Sources

- [GitHub Advisory Database: GHSA-8h6m-wv39-239m](https://github.com/advisories/GHSA-8h6m-wv39-239m)
- [OSV: GHSA-8h6m-wv39-239m](https://osv.dev/vulnerability/GHSA-8h6m-wv39-239m)
- <https://github.com/rancher/rancher/security/advisories/GHSA-8h6m-wv39-239m>
- <https://github.com/rancher/rancher/commit/7f16b596120dd382ce6e9ed0baf83bc23f633054>
- <https://github.com/rancher/rancher/commit/9c1d1c2bfcba36ae4f06c1fd043eb539ad801d4d>
- <https://github.com/rancher/rancher/commit/b0be28f86fc556414bd9b323f05b2b4bf8317c2d>
- <https://github.com/rancher/rancher/commit/f036e8b6ab726c3abbc03bbf7c8d0d53373c84e5>
- <https://github.com/rancher/rancher>
- <https://pkg.go.dev/vuln/GO-2025-3647>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8h6m-wv39-239m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8h6m-wv39-239m/>. Everything for agents: <https://agentprime.io/llms.txt>.
