Rancher EUVD-2026-53298

Exploitation requires a valid authenticated Rancher account with at minimum the default 'user' global role - the standard low-privilege role - and network reachability to the Rancher API/control plane; no admin rights, no user interaction, and no non-default configuration are needed. The single concrete prerequisite is the ability to set the Impersonate-User and/or Impersonate-Group HTTP headers on a request to Rancher, which the pre-fix SAR/impersonation middleware trusts blindly. Limiting factors: the attacker must already possess authenticated credentials (so fully anonymous exploitation is not possible) and must reach the Rancher endpoint; deployments that tightly restrict who receives Rancher accounts and that strip client impersonation headers at a proxy meaningfully reduce realistic risk.

The supplied CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H = 9.1) indicates a network-reachable, low-complexity, scope-changing attack with full C/I/A impact, which aligns with cross-cluster compromise. However, there is a notable discrepancy: the vector specifies PR:H, yet the description states the attacker only needs the default 'user' global role - the lowest standard authenticated role in Rancher - which is closer to PR:L; this makes the real-world barrier lower than PR:H implies and pushes true severity toward 9.9. EPSS was not provided and the CVE is not in CISA KEV, and no POC is referenced, so this is not confirmed as actively exploited; the risk is driven by ease of exploitation for any authenticated tenant rather than observed in-the-wild activity. In multi-tenant Rancher deployments where many users hold basic accounts, this is a genuine high priority because a single low-privilege account yields full platform and downstream-cluster takeover.

A low-privilege tenant who has been granted a normal Rancher account (default 'user' global role) sends an API request to the Rancher control plane adding an Impersonate-User: cluster-admin header (or Impersonate-Group: system:masters), causing the SAR middleware to authorize the request as a cluster administrator. With that elevated context the attacker reads all secrets, modifies configurations, and pivots into every downstream cluster Rancher manages. No public POC is referenced, but the low attack complexity and clear root cause in the fix diff make weaponization straightforward for anyone with a valid account.