Live › vulnerability › CVE-2026-88810
Rancher Manager's GlobalRole field inheritedNamespacedRules skipped the privilege-escalation check, so a non-admin user can be granted more permissions in downstream clusters than they already hold. An attacker with a low-privilege Rancher account can gain elevated access to the clusters Rancher manages.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 17:24 UTC. All times on this page are UTC.
Teams running SUSE Rancher Manager 2.15.2 or a Rancher Webhook in the affected ranges, where non-admin users receive global role bindings. The flaw reaches named namespaces in every downstream cluster the Rancher instance manages. Installations on other Rancher versions, or without these webhook versions, are not named as affected.
No product ranges from the sources yet.
2.15.2 as affected.0.11.0 through 0.11.4 and 0.12.0 through 0.12.1.0.11.4 or 0.12.1 to a fixed release (the exact fixed version is not stated in the sources).2.15.2: unknown fixed version in the sources.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A privilege escalation issue was discovered in Rancher Manager's role-based access control. The inheritedNamespacedRules field of a GlobalRole propagates permissions into named namespaces of every downstream cluster managed by the Rancher instance, but it was not subject to the privilege-escalation validation applied to the other permission-carrying fields of a GlobalRole. As a result, a non-administrative user could be granted, through a global role binding, permissions in downstream clusters that exceed the permissions that user already holds. This affected SUSE Rancher 2.15.2 only, and SUSE Rancher Webhook 0.11.0 up to 0.11.4, and 0.12.0 up to 0.12.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-88810")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.