Wazuh workflows before 44bf114 contain a shell injection vulnerability in GitHub Actions that allows attackers to execute arbitrary commands by submitting pull requests with crafted VERSION.json files. Attackers can inject shell metacharacters into environment variables that are directly interpolated into run steps, enabling command execution and exfiltration of secrets including GITHUB_TOKEN and AWS credentials on self-hosted runners.
CVE-2026-67308
CRITICALPre-NVD 10.010.0—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 10.0 from GitHub Security Advisory published 2026-08-01. a secondary CVSS source baseline 10.0; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 10.0Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 10.0
- EG Score
- 10.0(high)
- EG Risk
- 50(Track)EG Risk 50/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 1, 2026
Last Modified
August 1, 2026
Advisory Details (2)
Auto-updated Aug 1, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
Wazuh GitHub Actions Shell Injection via Fork Pull Request | Advisories | VulnCheck
https://www.vulncheck.com/advisories/wazuh-github-actions-shell-injection-via-fork-pull-requestgithub Patch Available🟡 PoC Available
GitHub Actions Shell Injection via Fork Pull Request · Advisory · wazuh/wazuh · GitHub
https://github.com/wazuh/wazuh/security/advisories/GHSA-95w2-gpvr-q4jhVendor Advisories for CVE-2026-67308(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 17:36 UTCEG score recompute
- 2026-08-01 17:36 UTCGHSA enrichment
- 2026-08-01 13:19 UTCEG score recompute
- 2026-08-01 12:44 UTCEG score recompute
- 2026-08-01 12:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(4)
What is CVE-2026-67308?
CVE-2026-67308 is a critical vulnerability published on August 1, 2026. Wazuh workflows before 44bf114 contain a shell injection vulnerability in GitHub Actions that allows attackers to execute arbitrary commands by submitting pull requests with crafted VERSION.json files. Attackers can inject shell metacharacters into environment variables that are directly…
When was CVE-2026-67308 disclosed?
CVE-2026-67308 was first published in the National Vulnerability Database on August 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-67308?
CVE-2026-67308 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-67308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67308, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-67308
Is Your Infrastructure Affected by CVE-2026-67308?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.