CVE-2025-32955: Step security/harden runner Harden-Runner Allows Evasion Of 'disable-sudo' Vulnerability

MODERATE
Advisory Identifier: GHSA-mxr3-8whj-j74r
CVSS 6.0
CWE-272 CWE-268 CWE-250
Published
Advisory Summary

CVE-2025-32955 is a MODERATE (CVSS 6.0) harden-runner allows evasion of 'disable-sudo' vulnerability (CWE-272: Least Privilege Violation) affecting Step security/harden runner libraries in the GitHub Actions ecosystem. The issue involves harden-runner allows evasion of 'disable-sudo' policy. Remediation is available by upgrading affected packages to version 2.12.0.

CVE-2025-32955 at a Glance

CVE Identifier CVE-2025-32955
GHSA Identifier GHSA-mxr3-8whj-j74r
Severity MODERATE
CVSS v3.1 Base Score 6.0
CWE Classification CWE-272: Least Privilege Violation
Affected Product Step security/harden runner
Package Ecosystem GitHub Actions
Published Date
Last Updated

Security Impact

CVSS: 6.0

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-32955

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

step-security/harden-runner fixed: 2.12.0
Upgrade step-security/harden-runner to 2.12.0
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 step-security/harden-runner

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-32955, inspect your project dependencies for Step security/harden runner:

inspect dependencies for step-security/harden-runner

Analyze the terminal output to locate any version of Step security/harden runner in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.12.0), 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-272: Least Privilege Violation, where the elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed. In Step security/harden runner, 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

### Summary Harden-Runner includes a policy option `disable-sudo` to prevent the GitHub Actions runner user from using sudo. This is implemented by removing the runner user from the sudoers file. However, this control can be bypassed as the runner user, being part of the docker group, can interact with the Docker daemon to launch privileged containers or access the host filesystem. This allows the attacker to regain root access or restore the sudoers file, effectively bypassing the restriction. For an attacker to bypass this control, they would first need the ability to run their malicious code (e.g., by a supply chain attack similar to tj-actions or exploiting a Pwn Request vulnerability)) on the runner. This vulnerability has been fixed in Harden-Runner version `v2.12.0`. ### Impact An attacker with the ability to run their malicious code on a runner configured with `disable-sudo: true` can escalate privileges to root using Docker, defeating the intended security control. ### Affected Configuration • Harden-Runner configurations that use `disable-sudo: true` on GitHub-hosted runners or on ephemeral self-hosted VM-based runners. • This issue does not apply to Kubernetes-based Actions Runner Controller (ARC) Harden-Runner. ### Mitigation / Fix This vulnerability has been fixed in Harden-Runner version `v2.12.0`. Users should migrate to the stronger `disable-sudo-and-containers` policy. This setting: • Disables sudo access, • Removes access to dockerd and containerd sockets, • Uninstalls Docker from the runner entirely, preventing container-based privilege escalation paths. ### Additional Improvements • The `disable-sudo` option will be deprecated in the future, as it does not sufficiently restrict privilege escalation on its own. • Harden-Runner now includes detections to alert on attempts to evade the `disable-sudo` policy. ### Credits Reported by @loresuso and @darryk10. We would like to thank them for collaborating with us to mitigate the vulnerability.

CVE-2025-32955 Affected Step security/harden runner Versions

1 component(s)
Fixed Versions:
2.12.0
Product / Package Ecosystem Affected Versions Fixed Version
step-security/harden-runner
GitHub Actions
≥ 0.12.0
< 2.12.0
2.12.0

References

Frequently Asked Questions

What is CVE-2025-32955?
CVE-2025-32955 is a security vulnerability in Step security/harden runner involving Harden-Runner allows evasion of 'disable-sudo' policy under CWE-272: Least Privilege Violation.
Which Step security/harden runner versions are affected?
Affected versions include releases prior to 2.12.0 across affected packages: step-security/harden-runner.
What version fixes CVE-2025-32955?
Upgrading to 2.12.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is step-security/harden-runner affected?
Yes, step-security/harden-runner is affected in releases prior to 2.12.0. Upgrade your dependency to 2.12.0 or later.
What is the CVSS score of CVE-2025-32955?
CVE-2025-32955 has a CVSS v3.1 base score of 6.0 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2025-32955?
CVE-2025-32955 is classified under CWE-272: Least Privilege Violation (The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.).
How can I check GitHub Actions dependencies for CVE-2025-32955?
Run the dependency tree command: 'inspect dependencies for step-security/harden-runner'. 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-mxr3-8whj-j74r",
  "modified" : "2025-04-22T01:07:03Z",
  "published" : "2025-04-22T01:07:03Z",
  "aliases" : [ "CVE-2025-32955" ],
  "summary" : "Harden-Runner allows evasion of 'disable-sudo' policy",
  "details" : "### Summary\nHarden-Runner includes a policy option `disable-sudo` to prevent the GitHub Actions runner user from using sudo. This is implemented by removing the runner user from the sudoers file. However, this control can be bypassed as the runner user, being part of the docker group, can interact with the Docker daemon to launch privileged containers or access the host filesystem. This allows the attacker to regain root access or restore the sudoers file, effectively bypassing the restriction. \n\nFor an attacker to bypass this control, they would first need the ability to run their malicious code (e.g., by a supply chain attack similar to tj-actions or exploiting a Pwn Request vulnerability)) on the runner. This vulnerability has been fixed in Harden-Runner version `v2.12.0`.\n\n### Impact\nAn attacker with the ability to run their malicious code on a runner configured with `disable-sudo: true` can escalate privileges to root using Docker, defeating the intended security control.\n\n### Affected Configuration\n•\tHarden-Runner configurations that use `disable-sudo: true` on GitHub-hosted runners or on ephemeral self-hosted VM-based runners.\n•\tThis issue does not apply to Kubernetes-based Actions Runner Controller (ARC) Harden-Runner.\n\n### Mitigation / Fix\nThis vulnerability has been fixed in Harden-Runner version `v2.12.0`. Users should migrate to the stronger `disable-sudo-and-containers` policy. This setting:\n•\tDisables sudo access,\n•\tRemoves access to dockerd and containerd sockets,\n•\tUninstalls Docker from the runner entirely, preventing container-based privilege escalation paths.\n\n\n### Additional Improvements\n•\tThe `disable-sudo` option will be deprecated in the future, as it does not sufficiently restrict privilege escalation on its own. \n•\tHarden-Runner now includes detections to alert on attempts to evade the `disable-sudo` policy.\n\n\n### Credits\nReported by @loresuso and @darryk10. We would like to thank them for collaborating with us to mitigate the vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "step-security/harden-runner"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.12.0"
      }, {
        "fixed" : "2.12.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/step-security/harden-runner/security/advisories/GHSA-mxr3-8whj-j74r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-32955"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/step-security/harden-runner/commit/0634a2670c59f64b4a01f0f96f84700a4088b9f0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/step-security/harden-runner"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/step-security/harden-runner/releases/tag/v2.12.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-250", "CWE-268", "CWE-272" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-22T01:07:03Z",
    "nvd_published_at" : "2025-04-21T21:15:20Z"
  }
}