{"answers":{"affected":"1 open source package ship an affected version, including step-security/harden-runner. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32946 in the wild and no public exploit code.","fix":"Upgrade step-security/harden-runner to 2.16.0 or later.","what":"CVE-2026-32946 is a medium-severity vulnerability in step-security harden-runner, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32946 and fix it if it is affected.\n\nWhat it is: CVE-2026-32946 is a medium-severity vulnerability in step-security harden-runner, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-32946 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- step-security/harden-runner (GitHub Actions): affected all versions; fixed in 2.16.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-2026-32946/ (Markdown: https://insights.sbomify.com/CVE-2026-32946/index.md)","id":"CVE-2026-32946","markdown":"https://insights.sbomify.com/CVE-2026-32946/index.md","name":"CVE-2026-32946","record":{"aliases":["GHSA-g699-3x6g-wm3g"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions security agent","requires_auth":"high_privilege","summary":"Attackers with code execution can bypass egress network restrictions by using TCP-based DNS queries, evading security controls in Harden-Runner.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"harden-runner","vendor":"stepsecurity"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"Harden-Runner is a CI/CD security agent that works like an EDR for GitHub Actions runners. In versions 2.15.1 and below, the Harden-Runner that allows bypass of the egress-policy: block network restriction using DNS queries over TCP. Egress policies are enforced on GitHub runners by filtering outbound connections at the network layer. When egress-policy: block is enabled with a restrictive allowed-endpoints list (e.g., only github.com:443), all non-compliant traffic should be denied. However, DNS queries over TCP, commonly used for large responses or fallback from UDP, are not adequately restricted. Tools like dig can explicitly initiate TCP-based DNS queries (+tcp flag) without being blocked. This vulnerability requires the attacker to already have code execution capabilities within the GitHub Actions workflow. The issue has been fixed in version 2.16.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":"Egress Policy Bypass via DNS over TCP in Harden-Runner (Community Tier)","id":"CVE-2026-32946","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Egress Policy Bypass via DNS over HTTPS (DoH) in Harden-Runner (Community Tier)","id":"CVE-2026-32947"},"packages":[{"ecosystem":"GitHub Actions","fixed":["2.16.0"],"introduced":["0"],"last_affected":[],"package":"step-security/harden-runner","purl":null,"source":"GHSA-g699-3x6g-wm3g"}],"prev":{"headline":"PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser","id":"CVE-2026-32945"},"products":["harden-runner"],"published":"2026-03-20","related":[{"cvss_score":6.3,"headline":"Bypassing Logging of Outbound Connections Using sendto, sendmsg, and sendmmsg in Harden-Runner (Community Tier)","id":"CVE-2026-25598","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":4.6,"headline":"Egress Policy Bypass via DNS over HTTPS (DoH) in Harden-Runner (Community Tier)","id":"CVE-2026-32947","kev_date_added":null,"published":"2026-03-20"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"2026-03-20","vendors":["step-security"]},"summary":"Attackers with code execution can bypass egress network restrictions by using TCP-based DNS queries, evading security controls in Harden-Runner.","url":"https://insights.sbomify.com/CVE-2026-32946/"}