CVE-2026-41052: SUSE Rancher privilege escalation in Project Owner role

CVE-2026-41052 · Severity: high · CVSS 8.4 · Published 2026-06-29

A vulnerability in Rancher Manager allows users with 'Project Owner' permissions to escalate their privileges to gain control over the underlying host server. By modifying security settings on their assigned projects, these users can bypass container isolation to access sensitive host-level resources and potentially compromise the entire cluster. This could lead to unauthorized data access, service disruption, or full takeover of the infrastructure.

Technologies: github.com/rancher/rancher (Go), Suse Rancher. Vendors: Go, Suse.

Quick answers

Is CVE-2026-41052 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41052 being exploited in the wild.
How severe is CVE-2026-41052?
High severity, with a CVSS score of 8.4, published 29 June 2026.
Which products and versions are affected?
github.com/rancher/rancher (Go) SEMVER:introduced=0,fixed=0.0.0-20260513182521-2800aaac25b5, SEMVER:introduced=2.14.0,fixed=2.14.2; Suse Rancher >= 2.14.0, < 2.14.2; >= 2.13.0, < 2.13.6; >= 2.12.0, < 2.12.10, >=2.12.0, <2.12.10; >=2.13.0, <2.13.6; >=2.14.0, <2.14.2.
Is there a fix for CVE-2026-41052?
Yes. github.com/rancher/rancher (Go): upgrade to 0.0.0-20260513182521-2800aaac25b5, 2.14.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41052 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41052?
Check whether you run github.com/rancher/rancher (Go) or Suse Rancher at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/rancher/rancher (Go): upgrade to 0.0.0-20260513182521-2800aaac25b5, 2.14.2 or later
    go get github.com/rancher/rancher@v2.14.2

Technical details

A privilege escalation vulnerability exists in Rancher Manager due to over-privileged default permissions in the 'project-owner' role. The role incorrectly uses a wildcard (*) permission for project resources, which includes the 'updatepsa' verb. An attacker with Project Owner and Cluster Member access can modify Pod Security Admission (PSA) labels on namespaces to apply a 'privileged' profile. This allows the deployment of containers that bypass standard isolation boundaries, enabling container breakout and access to host-level resources. The issue is resolved in versions 2.12.10, 2.13.6, and 2.14.2 by explicitly defining allowed verbs and removing 'updatepsa' from the default role.

Affected products

  • SUSE Rancher Manager >= 2.14.0, < 2.14.2; >= 2.13.0, < 2.13.6; >= 2.12.0, < 2.12.10

Identifiers

  • CVE-2026-41052
  • GHSA-vx8h-4prv-g744
  • GO-2026-5876

Timeline

  • 2026-05-27: disclosed: Initial disclosure date
  • 2026-06-29: advisory: NVD publication date
  • 2026-07-01: patched: GitHub Advisory updated with patch information

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.