# CVE-2026-67308: Wazuh GitHub Actions Shell Injection via Fork Pull Request

> Attackers can execute arbitrary commands and steal secrets by submitting crafted pull requests to Wazuh GitHub Actions workflows.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-95w2-gpvr-q4jh, GHSA-9chj-cp8j-3c5f

## What is CVE-2026-67308?

CVE-2026-67308 is a critical command injection vulnerability in wazuh, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-67308?


## How do I fix CVE-2026-67308?

No fix has been published for CVE-2026-67308 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67308 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67308 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67308 and fix it if it is affected.

What it is: CVE-2026-67308 is a critical command injection vulnerability in wazuh, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67308 exists.

Affected product: wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67308/ (Markdown: https://insights.sbomify.com/CVE-2026-67308/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67308
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67308
- OSV: https://osv.dev/vulnerability/CVE-2026-67308

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67308/
Summaries are generated and may contain mistakes; the official description above is the record.