# CVE-2026-88810: Privilege escalation in downstream clusters via GlobalRole inheritedNamespacedRules

Status: published. Published: 2026-11-02. Updated: 2026-11-02.

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.

## Remediation

- fix: github.com/rancher/webhook (go): GitHub reports patched versions 0.11.4. Check the advisory for the affected release branch. (source: GitHub GHSA-f898-2c8h-r7jc) — https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc
- fix: github.com/rancher/webhook (go): GitHub reports patched versions 0.12.1. Check the advisory for the affected release branch. (source: GitHub GHSA-f898-2c8h-r7jc) — https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc

## Affected products and versions

- SUSE / Rancher (Rancher): ≥ 2.15.2; < 2.15.3 (affected, semver). Source: CNA: suse
- SUSE / Rancher (Webhook): ≥ 0.11.0; < 0.11.4 (affected, semver); ≥ 0.12.0; < 0.12.1 (affected, semver). Source: CNA: suse
-  / github.com/rancher/webhook (github.com/rancher/webhook): >=0.11.0, <0.11.4 (affected, GitHub advisory range). Source: GitHub GHSA-f898-2c8h-r7jc
-  / github.com/rancher/webhook (github.com/rancher/webhook): >=0.12.0, <0.12.1 (affected, GitHub advisory range). Source: GitHub GHSA-f898-2c8h-r7jc
-  / github.com/rancher/rancher (github.com/rancher/rancher): >=2.15.2 (affected, GitHub advisory range). Source: GitHub GHSA-f898-2c8h-r7jc

## Severity and prioritization

- CVSS 3.1: 7.2 (high); CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H; source: CNA: suse

- CVSS 3.1: 7.2 (high); CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H; source: NVD: meissner@suse.de

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-306

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc (CNA: suse; vendor-advisory)

- https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc (meissner@suse.de)

- https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc (GitHub Security Advisories; advisory)

## Provenance

- CNA: suse: https://www.cve.org/CVERecord?id=CVE-2026-88810; retrieved 2026-11-02; source updated 2026-11-02

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88810; retrieved 2026-11-02; source updated 2026-11-02

- GitHub Security Advisories: https://github.com/rancher/webhook/security/advisories/GHSA-f898-2c8h-r7jc; retrieved 2026-11-02; source updated 2026-10-29

Revision: d49e7f2cd4293212685ebd68badee08b3c3c52d99be4c4ee2bb3632589035ee3

Canonical: https://y2.dev/cve/CVE-2026-88810

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.