CVE-2023-32199 is a medium-severity security vulnerability in github.com/rancher/rancher (go), affecting versions < 0.0.0-20251014212116-7faa74a968c2. It is fixed in 0.0.0-20251014212116-7faa74a968c2.
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 this category of attack. Patches This vulnerability is addressed by removing the corresponding ClusterRoleBindings whenever the admin GlobalRole or its GlobalRoleBindings are deleted. Previously orphaned ClusterRoleBindings are marked with the annotation authz.cluster.cattle.io/admin-globalrole-missing=true and should be deleted manually. Orphaned ClusterRoleBindings can be listed with: Patched versions of Rancher include releases v2.12.3, v2.11.7. Complications with the restricted admin functionality prevented the patches from being included in v2.10 and v2.9. Workarounds If the deployment can't be upgraded to a fixed version, users are advised to manually identify the orphaned ClusterRoleBindings and remove them. References If you have any questions or comments about this advisory: Contact the SUSE Rancher Security team for security related inquiries. Open an issue in the Rancher repository. Verify with our support matrix and product support lifecycle.
CVE-2023-32199 has a CVSS score of 4.3 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.0.0-20251014212116-7faa74a968c2). Upgrading removes the vulnerable code path.
go
github.com/rancher/rancher (< 0.0.0-20251014212116-7faa74a968c2)github.com/rancher/rancher → 0.0.0-20251014212116-7faa74a968c2 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2023-32199 is reachable in your applications. Explore open-source security for your team.
See if CVE-2023-32199 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2023-32199 in your environment →Upgrade github.com/rancher/rancher to 0.0.0-20251014212116-7faa74a968c2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2023-32199 is a medium-severity security vulnerability in github.com/rancher/rancher (go), affecting versions < 0.0.0-20251014212116-7faa74a968c2. It is fixed in 0.0.0-20251014212116-7faa74a968c2.
CVE-2023-32199 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/rancher/rancher (go) versions < 0.0.0-20251014212116-7faa74a968c2 is affected.
Yes. CVE-2023-32199 is fixed in 0.0.0-20251014212116-7faa74a968c2. Upgrade to this version or later.
Whether CVE-2023-32199 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/rancher/rancher to 0.0.0-20251014212116-7faa74a968c2 or later.