Rancher users retain access after moving namespaces into projects they don't have access to

Exploitation

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

CVSS

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

EPSS

• CVE-2020-10676: 1.03% estimated exploitation activity in the next 30 days; percentile 63.66 (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 was identified in which users with update privileges on a namespace, can move that namespace into a project they don't have access to. After the namespace transfer is completed, their previous permissions are still preserved, which enables them to gain access to project-specific resources (such as project secrets). In addition, resources in the namespace will now count toward the quota limit of the new project, potentially causing availability issues. User with roles Project Owner and Project Member on the source project can exploit this vulnerability; however, this would also apply to custom roles with similar privileges. The patched version include an improved RBAC mechanism, which checks if the user has the correct permissions before the namespace move takes place. Patches Patched versions include releases 2.6.13, 2.7.4 and later versions. Workarounds There is no direct mitigation besides updating Rancher to a patched version. For more information If you…

Published by the source

6 Jun 2023, 01:59 UTC

Last modified by the source

14 Dec 2023, 22:28 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8vhc-hwhc-cpj4

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

# Patch Next advisory brief: CVE-2020-10676

Advisory: Rancher users retain access after moving namespaces into projects they don't have access to
IDs: CVE-2020-10676, GHSA-8vhc-hwhc-cpj4
Record: https://patchnext.com/advisories/cve-2020-10676 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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.7.4, 2.6.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/rancher: affected >= 2.6.0, < 2.6.13; >= 2.7.0, < 2.7.4; fixed in 2.6.13, 2.7.4

## 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-8vhc-hwhc-cpj4 (GitHub-reviewed advisory GHSA-8vhc-hwhc-cpj4 lists affected ranges: Go github.com/rancher/rancher >=2.6.0 =2.7.0 <2.7.4)

Commands are suggestions: review each one before running it.