CVE-2026-25598
Audit Logging Bypass in Harden-Runner GitHub Action via Socket Calls
Publication date: 2026-02-09
Last updated on: 2026-02-28
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| stepsecurity | harden-runner | to 2.14.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-778 | When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Harden-Runner GitHub Action (Community Tier) prior to version 2.14.2. It allows outbound network connections to bypass audit logging. Specifically, when using the egress-policy set to audit, outbound traffic that uses the sendto, sendmsg, and sendmmsg socket system calls can evade detection and logging.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing certain outbound network connections to go undetected and unlogged. This means that potentially malicious or unauthorized network traffic could occur without being recorded, reducing the effectiveness of security monitoring and incident response.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in Harden-Runner version 2.14.2. Immediate mitigation should include upgrading the Harden-Runner GitHub Action (Community Tier) to version 2.14.2 or later to ensure that outbound network connections using sendto, sendmsg, and sendmmsg socket system calls are properly audited and logged.