Skip to main content
VulnerabilityPublished

CVE-2023-32199: SUSE rancher · Improper Preservation of Permissions

Affects SUSE rancherSource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubrancher/rancherpkg:github/rancher/rancherOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, European organizations should implement specific mitigations to reduce risk from CVE-2023-32199: 1) Conduct a thorough audit of all custom GlobalRoles in Rancher, focusing on those with wildcard '*' permissions on resources or non-resource URLs. 2) Avoid using overly permissive wildcard rules in GlobalRoles; instead, apply the principle of least privilege by defining explicit and minimal permissions. 3) After removing or modifying GlobalRoles, manually verify that associated user access to clusters has been revoked by testing access or reviewing audit logs. 4) Implement strict monitoring and alerting on Rancher access logs to detect any anomalous or unauthorized cluster access, especially from users whose roles have been revoked. 5) Enforce multi-factor authentication (MFA) and strong credential hygiene for all users with administrative privileges to reduce risk of account compromise. 6) Limit the number of users with high privilege roles and regularly review role assignments. 7) Stay informed on SUSE Rancher security advisories and apply patches promptly once available. 8) Consider network segmentation and additional Kubernetes RBAC controls to limit the blast radius of any unauthorized access. These steps go beyond generic advice by focusing on role auditing, permission minimization, and active verification of access revocation.

Description

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 or have a * on * rule for non-resource URLs

References

Community reviews

Loading reviews…