Rancher has Privilege Escalation from Project Owner to Host
Published 1 Jul 2026 · Updated 10 Sept 2026
Is your project on an affected github.com/rancher/rancher?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.14.0 <2.14.2
- Fixed in
- 2.14.2
go get github.com/rancher/rancher@v2.14.2- Affected
- >=2.13.0 <2.13.6
- Fixed in
- 2.13.6
go get github.com/rancher/rancher@v2.13.6- Affected
- >=2.12.0 <2.12.10
- Fixed in
- 2.12.10
go get github.com/rancher/rancher@v2.12.10- Affected
- <0.0.0-20260513182521-2800aaac25b5
- Fixed in
- 0.0.0-20260513182521-2800aaac25b5
go get github.com/rancher/rancher@v0.0.0-20260513182521-2800aaac25b5Details
Impact
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: 1. Cluster Access: The user is granted Cluster Member access. 2. Project Ownership: The user creates or is assigned ownership of a project. 3. Namespace Creation: The user creates a namespace within that project. 4. PSA Modification: The user modifies the namespace PSA configuration to use the privileged profile. 5. 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:
- Deployment of privileged containers
- Access to host-level resources
- Container breakout
- Cluster privilege escalation
- Compromise of workloads running on affected nodes
Please refer to the associated MITRE ATT&CK techniques for further information about this category of attack:
Reference: Kubernetes Pod Security Standards — Privileged Profile
Patches
This vulnerability is resolved by modifying the project-owner role to explicitly define the allowed verbs for projects resources instead of using the wildcard (*) permission.
The updated role configuration removes access to the updatepsa verb. This prevents project owners from modifying PSA settings in a manner that could enable privilege escalation.
Patched versions of Rancher include releases v2.12.10, v2.13.6, and v2.14.2.
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.
References
If you have any questions or comments about this advisory:
- Reach out to the SUSE Rancher Security team for security related inquiries.
- Open an issue in the Rancher repository.
- Verify with our support matrix and product support lifecycle.
Is GHSA-vx8h-4prv-g744 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/rancher/rancher, and gives you the command that fixes it.
More advisories for github.com/rancher/rancher
- LowCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider in github.com/rancher/rancher · 7 Jul 2026
- LowCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter in github.com/rancher/rancher · 7 Jul 2026
- HighCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider · 1 Jul 2026
- CriticalCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter · 1 Jul 2026
- LowCVE-2026-25705Rancher Extensions have arbitrary file access via path traversal in github.com/rancher/rancher · 25 Jun 2026
- HighCVE-2026-25705Rancher Extensions have arbitrary file access via path traversal · 7 May 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.