CVE-2026-41052: 
Rancher vulnerability analysis and mitigation

CVE-2026-41052 is a privilege escalation vulnerability in SUSE Rancher titled "Privilege Escalation from Project Owner to Host." It allows users with the Project Owner role to escalate their privileges to host-level access by manipulating Pod Security Admission (PSA) labels on namespaces. Affected versions include Rancher 2.12.0–2.12.9, 2.13.0–2.13.5, and 2.14.0–2.14.1. The vulnerability was published on May 27, 2026, and disclosed via NVD on June 29, 2026. It carries a CVSS v3.1 score of 8.8 (High) and a CVSS v4.0 score of 9.4 (Critical) (GitHub Advisory, GHSA).

The root cause is improper privilege management (CWE-269 estimated; formally classified as CWE-305 Authentication Bypass by Primary Weakness), stemming from the Project Owner role being configured with wildcard (*) permissions on project resources, which inadvertently grants access to the updatepsa verb. This allows a Project Owner to modify Pod Security Admission labels on namespaces within their project, setting the PSA profile to privileged — which disables core Kubernetes security protections. The attack chain requires the attacker to hold Cluster Member access, own or create a project, create a namespace within it, modify its PSA configuration, and then deploy privileged workloads to escape container isolation boundaries (GitHub Advisory, GHSA).

Successful exploitation enables a Project Owner to break out of container isolation and gain access to host-level resources on affected Kubernetes nodes. Concrete impacts include deployment of privileged containers, container breakout to the underlying host, cluster-wide privilege escalation, and compromise of other workloads running on affected nodes. This results in full confidentiality, integrity, and availability impact on both the vulnerable system and subsequent systems within the cluster environment (GitHub Advisory, GHSA).

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported as of the time of disclosure (GHSA). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.032% (0.000320), placing it in the 24th percentile for exploitation probability within 30 days. Exploitation requires the attacker to already hold a Project Owner role within a Rancher-managed cluster, limiting the attack surface to authenticated, privileged users (GHSA).

1. Obtain Cluster Member Access: The attacker must first be granted or acquire Cluster Member access on a target Rancher-managed Kubernetes cluster running an affected version (2.12.0–2.12.9, 2.13.0–2.13.5, or 2.14.0–2.14.1).
2. Acquire Project Owner Role: The attacker creates a new project within the cluster or is assigned ownership of an existing project, gaining the Project Owner role.
3. Create a Namespace: Within the owned project, the attacker creates a new namespace (or uses an existing one they control).
4. Modify PSA Labels: Leveraging the wildcard * permission on project resources (which includes the updatepsa verb), the attacker modifies the namespace's Pod Security Admission labels to set the security profile to privileged (e.g., pod-security.kubernetes.io/enforce: privileged).
5. Deploy Privileged Workloads: The attacker deploys a privileged container (e.g., with securityContext.privileged: true) within the modified namespace. The privileged profile disables standard Kubernetes security controls.
6. Achieve Host-Level Access: From within the privileged container, the attacker mounts host filesystems, accesses host processes, or uses kernel capabilities to break out of the container and gain control of the underlying node, enabling lateral movement across the cluster (GitHub Advisory, GHSA).

• Logs: Rancher audit logs showing a Project Owner user invoking the updatepsa verb on a namespace resource; Kubernetes API server logs recording changes to pod-security.kubernetes.io/enforce labels on namespaces being set to privileged.
• Kubernetes Events: Namespace label modification events (kubectl get events) showing PSA label changes from a non-admin user; creation of pods with securityContext.privileged: true in namespaces not previously configured as privileged.
• File System (Host): Unexpected access to host-level paths (e.g., /proc, /sys, /dev) from container processes; new files or scripts written to host filesystem paths from within a container.
• Process: Privileged container processes with host PID or network namespace access (--pid=host, --net=host); unexpected child processes spawned with elevated capabilities on cluster nodes.
• Network: Unusual outbound connections from cluster nodes initiated by container workloads; lateral movement traffic between nodes originating from a compromised container (GitHub Advisory).

SUSE has released patched versions of Rancher: v2.12.10, v2.13.6, and v2.14.2. Upgrading to one of these versions is the recommended remediation, as the fix modifies the Project Owner role to explicitly enumerate allowed verbs for project resources (removing the wildcard *) and revokes access to the updatepsa verb. As a workaround for environments where immediate upgrade is not feasible, administrators should create a custom project role based on Project Owner but restrict the allowed verbs for project resources to: get, update, delete, patch, create, list, watch, deletecollection — explicitly excluding updatepsa. Additionally, administrators should restrict Project Owner role assignments to only trusted users (GitHub Advisory, GHSA).

Security Online Info covered the vulnerability as part of a broader report on Rancher security flaws involving cluster privilege escalation. The advisory was credited to researchers MMunier and Trolldemorted as finders. No significant social media controversy or widespread community debate has been observed beyond standard vulnerability tracking and aggregation activity (Security Online, GitHub Advisory).