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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-22031: 0.43% estimated exploitation activity in the next 30 days; percentile 37.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Please consult the associated MITRE ATT&CK - Technique - Privilege Escalation for further information about this category of attack. Patches Patched versions include releases v2.11.1, v2.10.5, v2.9.9. The fix involves the following changes: Rancher: - Instead of using the project name as the namespace, Rancher will instead be using a new field on the project spec called backingNamespace. If that field exists, use that for the project namespace going forward. However, if the project does not have that field filled…

Published by the source

25 Apr 2025, 15:09 UTC

Last modified by the source

23 May 2025, 18:36 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8h6m-wv39-239m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-22031

Advisory: Rancher users who can create Projects can gain access to arbitrary projects
IDs: CVE-2024-22031, GHSA-8h6m-wv39-239m
Record: https://patchnext.com/advisories/cve-2024-22031 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/rancher 2.11.1, 2.10.5, 2.9.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/rancher: 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

## Suggested inspection (read-only)
- Go github.com/rancher/rancher: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rancher/rancher.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8h6m-wv39-239m (GitHub-reviewed advisory GHSA-8h6m-wv39-239m lists affected ranges: Go github.com/rancher/rancher >=2.8.0 =2.10.0 =2.11.0 <2.11.1)

Commands are suggestions: review each one before running it.