All vulnerabilities

Servers and applications

CVE-2026-41052

Privilege Escalation from Project Owner to Host

Severity
Critical 9.4
Published
27 May 2026
Last changed
25 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.12.10, 2.13.6, 2.14.2
Exploit chance
0.4% in the next 30 daysHigher than 37% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-305
Attack
Over the network · Needs an administrator account · No user action needed
Attacker can
Read data · Change data · Take it down
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-vx8h-4prv-g744
Sources
NVD, Project advisories (GitHub)

Description

A vulnerability has been identified in Rancher Manager that allows users assigned the Project Owner role to modify Pod Security Admission (PSA) labels on namespaces within their projects. Under the default role configuration, an attacker with the following access pattern can exploit this issue:

  • Cluster Access: The user is granted Cluster Member access.
  • Project Ownership: The user creates or is assigned ownership of a project.
  • Namespace Creation: The user creates a namespace within that project.
  • PSA Modification: The user modifies the namespace PSA configuration to use the privileged profile.
  • Privilege Escalation: The user deploys privileged workloads within the namespace.

As outlined in the Kubernetes Pod Security Standards documentation, privileged containers disable core Kubernetes security protections, allowing workloads to bypass standard container isolation boundaries. This can result in privilege escalation within the cluster environment.

Potential impacts include:

From rancher/rancher's security advisory. Shortened; the full text is there.

Workarounds

If upgrading is not immediately possible, administrators should create a custom project role based on the existing Project Owner role, while removing unrestricted wildcard permissions for project resources.

The allowed verbs for projects should be restricted to: “get, update, delete, patch, create, list, watch, deletecollection” instead of “*”.

This prevents access to the updatepsa capability that enables the privilege escalation path.

Workarounds as given by rancher/rancher's security advisory.

Affected software

SoftwareAffected versions
RancherServers and applications · cpe:a:suse:rancher
  • From 2.12.0 before 2.12.10
  • From 2.13.0 before 2.13.6
  • From 2.14.0 before 2.14.2
RancherServers and applications · github:rancher/rancher
  • From 2.12.0 before 2.12.10
  • From 2.13.0 before 2.13.6
  • From 2.14.0 before 2.14.2

About Rancher

Complete container management platform

From its GitHub repository.
Teams using it daily
More than 30,000Rancher
Docker Hub pulls
320,721,144Docker Hub, 15 Nov 2026
GitHub stars
26,057GitHub, 15 Nov 2026
Forks
3,226GitHub, 15 Nov 2026
Latest release
v2.15.3GitHub, 15 Nov 2026
Released
29 Oct 2026GitHub
License
Apache-2.0GitHub
First published on GitHub
7 Nov 2014GitHub

Release lines

ReleaseLatestSecurity fixes
2.152.15.3Until 27 Feb 2028
2.142.14.7Until 10 Oct 2027
2.132.13.11Until 17 Jun 2027
2.122.12.15Until 28 Feb 2027
2.112.11.19Ended 24 Oct 2026
2.102.10.12Ended 19 Jun 2026

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-41052
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41052
  • GitHub Advisory Database https://github.com/advisories/GHSA-vx8h-4prv-g744
  • github.com https://github.com/rancher/rancher/security/advisories/GHSA-vx8h-4prv-g744