Rancher user retains access to clusters despite Global Role removal

Exploitation

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

CVSS

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

EPSS

• CVE-2023-32199: 0.22% estimated exploitation activity in the next 30 days; percentile 12.82 (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 Manager, where after removing a custom GlobalRole that gives administrative access or the corresponding binding, the user still retains access to clusters. This only affects custom Global Roles that: - Have a on in rule for resources - Have a on rule for non-resource URLs For example Specifically: - When a user is bound to a custom admin GlobalRole, a corresponding ClusterRoleBinding is created on all clusters that binds them to the cluster-admin ClusterRole. - When such a GlobalRole or the GlobalRoleBinding (e.g., when the user is unassigned from this role in UI) is deleted, the ClusterRoleBinding that binds them to the cluster-admin ClusterRole stays behind. This issue allows a user to continue having access to clusters after they have been unassigned from the custom admin global role or the role has been deleted. Please consult the associated MITRE ATT&CK - Technique - Account Access Removal for further information about…

Published by the source

24 Oct 2025, 15:06 UTC

Last modified by the source

29 Oct 2025, 15:42 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j4vr-pcmw-hx59

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

# Patch Next advisory brief: CVE-2023-32199

Advisory: Rancher user retains access to clusters despite Global Role removal
IDs: CVE-2023-32199, GHSA-j4vr-pcmw-hx59
Record: https://patchnext.com/advisories/cve-2023-32199 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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 0.0.0-20251014212116-7faa74a968c2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/rancher: affected < 0.0.0-20251014212116-7faa74a968c2; fixed in 0.0.0-20251014212116-7faa74a968c2

## 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-j4vr-pcmw-hx59 (GitHub-reviewed advisory GHSA-j4vr-pcmw-hx59 lists affected ranges: Go github.com/rancher/rancher >=0 <0.0.0-20251014212116-7faa74a968c2)

Commands are suggestions: review each one before running it.