Wazuh workflows before 44bf114 contain a shell injection vulnerability in GitHub Actions that allows attackers to execute arbitrary commands by… (CVE-2026-67308)
Wazuh workflows prior to commit 44bf114 contain a shell injection vulnerability in their GitHub Actions. This flaw allows attackers to execute arbitrary commands by submitting pull requests with specially crafted VERSION.json files. The vulnerability arises from shell metacharacters being injected into environment variables that are directly used in run steps. Exploitation can lead to command execution and exfiltration of sensitive secrets such as GITHUB_TOKEN and AWS credentials on self-hosted runners.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-67308 affects Wazuh workflows before commit 44bf114. It is a shell injection issue (CWE-78) in GitHub Actions workflows where environment variables interpolated directly into run steps can be manipulated by attackers submitting malicious VERSION.json files in pull requests. This enables arbitrary command execution and potential leakage of sensitive tokens and credentials on self-hosted runners. The CVSS v3.1 score is 10.0, indicating critical severity with network attack vector, low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability.
Potential Impact
Successful exploitation allows remote unauthenticated attackers to execute arbitrary shell commands within the context of the GitHub Actions runner. This can lead to full compromise of the runner environment, including exfiltration of sensitive secrets such as GITHUB_TOKEN and AWS credentials. The impact affects confidentiality, integrity, and availability of the affected systems.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or patch is released, avoid running untrusted pull requests on self-hosted GitHub Actions runners or implement strict validation and sanitization of inputs used in workflows. Monitor vendor channels for updates regarding a fix.
Wazuh workflows before 44bf114 contain a shell injection vulnerability in GitHub Actions that allows attackers to execute arbitrary commands by… (CVE-2026-67308)
Description
Wazuh workflows prior to commit 44bf114 contain a shell injection vulnerability in their GitHub Actions. This flaw allows attackers to execute arbitrary commands by submitting pull requests with specially crafted VERSION.json files. The vulnerability arises from shell metacharacters being injected into environment variables that are directly used in run steps. Exploitation can lead to command execution and exfiltration of sensitive secrets such as GITHUB_TOKEN and AWS credentials on self-hosted runners.
CVSS v3.1
Score 10.0critical
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-67308 affects Wazuh workflows before commit 44bf114. It is a shell injection issue (CWE-78) in GitHub Actions workflows where environment variables interpolated directly into run steps can be manipulated by attackers submitting malicious VERSION.json files in pull requests. This enables arbitrary command execution and potential leakage of sensitive tokens and credentials on self-hosted runners. The CVSS v3.1 score is 10.0, indicating critical severity with network attack vector, low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability.
Potential Impact
Successful exploitation allows remote unauthenticated attackers to execute arbitrary shell commands within the context of the GitHub Actions runner. This can lead to full compromise of the runner environment, including exfiltration of sensitive secrets such as GITHUB_TOKEN and AWS credentials. The impact affects confidentiality, integrity, and availability of the affected systems.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or patch is released, avoid running untrusted pull requests on self-hosted GitHub Actions runners or implement strict validation and sanitization of inputs used in workflows. Monitor vendor channels for updates regarding a fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9chj-cp8j-3c5f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67308"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6e6294bf32cb7a344f6946
Added to database: 08/01/2026, 21:18:12 UTC
Last enriched: 08/01/2026, 21:21:57 UTC
Last updated: 08/02/2026, 00:03:46 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.