CVE-2026-41052: Github.com/rancher/rancher Rancher Has Privilege Escalation From Vulnerability

CRITICAL
Advisory Identifier: GHSA-vx8h-4prv-g744
CVSS 8.4
CWE-305
Published
Advisory Summary

CVE-2026-41052 is a CRITICAL (CVSS 8.4) rancher has privilege escalation from vulnerability (CWE-305: Authentication Bypass by Primary Weakness) affecting Github.com/rancher/rancher libraries in the Go ecosystem. The issue involves rancher has privilege escalation from project owner to host. Remediation is available by upgrading affected packages to version 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5.

CVE-2026-41052 at a Glance

CVE Identifier CVE-2026-41052
GHSA Identifier GHSA-vx8h-4prv-g744
Severity CRITICAL
CVSS v3.1 Base Score 8.4
CWE Classification CWE-305: Authentication Bypass by Primary Weakness
Affected Product Github.com/rancher/rancher
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-41052

To remediate this vulnerability, upgrade all affected Github.com/rancher/rancher dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rancher/rancher fixed: 2.14.2
Upgrade github.com/rancher/rancher to 2.14.2
github.com/rancher/rancher fixed: 2.13.6
Upgrade github.com/rancher/rancher to 2.13.6
github.com/rancher/rancher fixed: 2.12.10
Upgrade github.com/rancher/rancher to 2.12.10
github.com/rancher/rancher fixed: 0.0.0-20260513182521-2800aaac25b5
Upgrade github.com/rancher/rancher to 0.0.0-20260513182521-2800aaac25b5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rancher/rancher

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-41052, inspect your project dependencies for Github.com/rancher/rancher:

inspect dependencies for github.com/rancher/rancher

Analyze the terminal output to locate any version of Github.com/rancher/rancher in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.14.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-305: Authentication Bypass by Primary Weakness, where the authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. In Github.com/rancher/rancher, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://kubernetes.io/docs/concepts/security/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: - [Deploy Container](https://attack.mitre.org/techniques/T1610/) - [Escape to Host](https://attack.mitre.org/techniques/T1611/) - [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068) Reference: [Kubernetes Pod Security Standards — Privileged Profile](https://kubernetes.io/docs/concepts/security/pod-security-standards/#privileged) ### 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](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

CVE-2026-41052 Affected Github.com/rancher/rancher Versions

4 component(s)
Fixed Versions:
2.14.22.13.62.12.100.0.0-20260513182521-2800aaac25b5
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rancher/rancher
Go
≥ 2.14.0
< 2.14.2
2.14.2
github.com/rancher/rancher
Go
≥ 2.13.0
< 2.13.6
2.13.6
github.com/rancher/rancher
Go
≥ 2.12.0
< 2.12.10
2.12.10
github.com/rancher/rancher
Go
< 0.0.0-20260513182521-2800aaac25b5
0.0.0-20260513182521-2800aaac25b5

References

Frequently Asked Questions

What is CVE-2026-41052?
CVE-2026-41052 is a security vulnerability in Github.com/rancher/rancher involving Rancher has Privilege Escalation from Project Owner to Host under CWE-305: Authentication Bypass by Primary Weakness.
Which Github.com/rancher/rancher versions are affected?
Affected versions include releases prior to 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5 across affected packages: github.com/rancher/rancher.
What version fixes CVE-2026-41052?
Upgrading to 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/rancher affected?
Yes, github.com/rancher/rancher is affected in releases prior to 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5. Upgrade your dependency to 2.14.2, 2.13.6, 2.12.10, 0.0.0-20260513182521-2800aaac25b5 or later.
What is the CVSS score of CVE-2026-41052?
CVE-2026-41052 has a CVSS v3.1 base score of 8.4 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-41052?
CVE-2026-41052 is classified under CWE-305: Authentication Bypass by Primary Weakness (The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.).
How can I check Go dependencies for CVE-2026-41052?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/rancher'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vx8h-4prv-g744",
  "modified" : "2026-07-01T20:57:49Z",
  "published" : "2026-07-01T20:57:49Z",
  "aliases" : [ "CVE-2026-41052" ],
  "summary" : "Rancher has Privilege Escalation from Project Owner to Host",
  "details" : "### Impact\n\nA 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:\n1. **Cluster Access:** The user is granted Cluster Member access.\n2. **Project Ownership:** The user creates or is assigned ownership of a project.\n3. **Namespace Creation:** The user creates a namespace within that project.\n4. **PSA Modification:** The user modifies the namespace PSA configuration to use the privileged profile.\n5. **Privilege Escalation:** The user deploys privileged workloads within the namespace.\n\nAs outlined in the [Kubernetes Pod Security Standards](https://kubernetes.io/docs/concepts/security/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.\n\nPotential impacts include:\n- Deployment of privileged containers\n- Access to host-level resources\n- Container breakout\n- Cluster privilege escalation\n- Compromise of workloads running on affected nodes\n\nPlease refer to the associated MITRE ATT&CK techniques for further information about this category of attack:\n- [Deploy Container](https://attack.mitre.org/techniques/T1610/)\n- [Escape to Host](https://attack.mitre.org/techniques/T1611/)\n- [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068)\n\nReference:\n[Kubernetes Pod Security Standards — Privileged Profile](https://kubernetes.io/docs/concepts/security/pod-security-standards/#privileged)\n\n### Patches\nThis vulnerability is resolved by modifying the `project-owner` role to explicitly define the allowed verbs for `projects` resources instead of using the wildcard `(*)` permission.\n\nThe 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.\n\nPatched versions of Rancher include releases `v2.12.10`, `v2.13.6`, and `v2.14.2`.\n\n### Workarounds\nIf 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.\n\nThe allowed verbs for projects should be restricted to: “`get`, `update`, `delete`, `patch`, `create`, `list`, `watch`, `deletecollection`” instead of “`*`”.\n\nThis prevents access to the `updatepsa` capability that enables the privilege escalation path.\n\n### References\nIf you have any questions or comments about this advisory:\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.14.0"
      }, {
        "fixed" : "2.14.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.13.0"
      }, {
        "fixed" : "2.13.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.12.0"
      }, {
        "fixed" : "2.12.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260513182521-2800aaac25b5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/security/advisories/GHSA-vx8h-4prv-g744"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41052"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/pull/55061"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/commit/2800aaac25b5a2c448f800e1f46d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rancher/rancher"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-305" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-01T20:57:49Z",
    "nvd_published_at" : "2026-06-29T16:16:39Z"
  }
}