CVE-2026-32946: Egress Policy Bypass via DNS over TCP in Harden-Runner (Community Tier)
Summary A vulnerability exists in the Community Tier of Harden-Runner that allows bypassing the egress-policy: block network restriction using DNS queries over TCP. Harden-Runner enforces egress policies on GitHub runners by filtering outbound connections at the network layer.
Published Mar 17, 2026 · Updated Mar 20, 2026
Affected packages
step-security/harden-runner
- Ecosystem
- GitHub Actions
- Affected
- <= 2.15.1
- Fixed in
- 2.16.0
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A vulnerability exists in the Community Tier of Harden-Runner that allows bypassing the egress-policy: block network restriction using DNS queries over TCP.
Harden-Runner enforces egress policies 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 Enterprise Tier of Harden-Runner is not affected by this vulnerability.
Impact
When Harden-Runner is configured with egress-policy: block and a restrictive allowed-endpoints list, an attacker with existing code execution capabilities within a GitHub Actions workflow can bypass the egress block policy by initiating DNS queries over TCP to external resolvers. This allows outbound network communication that evades the configured network restrictions.
This vulnerability affects only the Community Tier. It requires the attacker to already have code execution capabilities within the GitHub Actions workflow.
Remediation
For Community Tier Users
Upgrade to Harden-Runner v2.16.0 or later.
For Enterprise Tier Users
No action required. Enterprise tier customers are not affected by this vulnerability.
Credit
We would like to thank Devansh Batham for responsibly disclosing this vulnerability through our security reporting process.
Credited to devanshbatham.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More GitHub Actions vulnerabilities
All GitHub Actions entriesCVE-2026-32947
Egress Policy Bypass via DNS over HTTPS (DoH) in Harden-Runner (Community Tier)
medium4.6Mar 17, 2026CVE-2026-25598
Harden-Runner: Bypassing Logging of Outbound Connections Using sendto, sendmsg, and sendmmsg in Harden-Runner (Community Tier)
medium6.0Feb 9, 2026CVE-2025-32955
Harden-Runner allows evasion of 'disable-sudo' policy
medium6.0Apr 22, 2025CVE-2024-52587
Harden-Runner has a command injection weaknesses in `setup.ts` and `arc-runner.ts`
low8.8Nov 18, 2024
