Loading vulnerability…
CVE-2026-67308 is a critical OS command injection vulnerability in Wazuh GitHub Actions workflows prior to commit 44bf114. The flaw arises when attacker-controlled data from VERSION.json in a pull request is written into GitHub Actions environment variables and later interpolated directly into shell run steps within workflows and composite actions. Because the value is incorporated into shell execution without safe handling, shell metacharacters embedded in the attacker-supplied input can be interpreted by the shell and executed as commands. The issue is reachable through pull_request-triggered CI workflows, including pull requests from public forks, creating a direct path from untrusted repository content to command execution in the CI/CD environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical OS command/shell injection vulnerability in Wazuh GitHub Actions workflows that can allow arbitrary command execution on self-hosted runners via crafted VERSION.json data in pull requests, potentially exposing secrets and enabling CI/CD supply-chain compromise.
A shell injection vulnerability in Wazuh GitHub Actions workflows before commit 44bf114 that can allow arbitrary command execution via crafted pull requests and VERSION.json files, potentially exposing secrets such as GITHUB_TOKEN and AWS credentials on self-hosted runners.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.