GITHUB-ACTIONS · AUGUST 2026 · EARLY WARNING

Wazuh GitHub Actions Vulnerability: Shell Injection Threat

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

CVE-2026-67308Severity: CRITICAL

Wazuh workflows before version 44bf114 reportedly contain a shell injection vulnerability in GitHub Actions, allowing attackers to execute arbitrary commands and exfiltrate secrets.

What happened

An early warning has been issued regarding a critical shell injection vulnerability (CVE-2026-67308) in Wazuh GitHub Actions workflows prior to version 44bf114. This vulnerability allows attackers to inject shell metacharacters into environment variables, enabling command execution and potential exfiltration of secrets such as GITHUB_TOKEN and AWS credentials on self-hosted runners. It is under investigation how this vulnerability may be related to the recently discovered ChainDrop npm worm, which has infected over 400 packages. Software engineers using affected Wazuh workflows are advised to upgrade to version 44bf114 or later and review self-hosted runners for signs of compromise. For more details, consult the primary sources provided.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If github actions is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats