{"answers":{"affected":"1 open source package ship an affected version, including step-security/harden-runner.","exploited":"There is no known exploitation of CVE-2025-32955 in the wild and no public exploit code.","fix":"Upgrade step-security/harden-runner to 2.12.0 or later.","what":"CVE-2025-32955 is a medium-severity vulnerability in step-security harden-runner, published on 21 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32955 and fix it if it is affected.\n\nWhat it is: CVE-2025-32955 is a medium-severity vulnerability in step-security harden-runner, published on 21 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32955 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- step-security/harden-runner (GitHub Actions): affected from 0.12.0; fixed in 2.12.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32955/ (Markdown: https://insights.sbomify.com/CVE-2025-32955/index.md)","id":"CVE-2025-32955","markdown":"https://insights.sbomify.com/CVE-2025-32955/index.md","name":"CVE-2025-32955","record":{"aliases":["GHSA-mxr3-8whj-j74r"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"CI/CD security agent","requires_auth":"high_privilege","summary":"Attackers can bypass sudo restrictions in Harden-Runner by leveraging Docker group membership to gain root access on CI/CD runners.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-268","name":"Privilege Chaining"}],"description":"Harden-Runner is a CI/CD security agent that works like an EDR for GitHub Actions runners. Versions from 0.12.0 to before 2.12.0 are vulnerable to `disable-sudo` bypass. 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. This issue has been patched in version 2.12.0.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Harden-Runner Evasion of 'disable-sudo' policy","id":"CVE-2025-32955","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":1,"n_references":3,"next":{"headline":"ManageWiki has SQL injection vulnerability in NamespaceMigrationJob","id":"CVE-2025-32956"},"packages":[{"ecosystem":"GitHub Actions","fixed":["2.12.0"],"introduced":["0.12.0"],"last_affected":[],"package":"step-security/harden-runner","purl":null,"source":"GHSA-mxr3-8whj-j74r"}],"prev":{"headline":"z80pack Vulnerable to Exposure of the GITHUB_TOKEN in Workflow Run Artifact","id":"CVE-2025-32953"},"products":["harden-runner"],"published":"2025-04-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["step-security"]},"summary":"Attackers can bypass sudo restrictions in Harden-Runner by leveraging Docker group membership to gain root access on CI/CD runners.","url":"https://insights.sbomify.com/CVE-2025-32955/"}