# CVE-2026-54085: Wazuh: Missing input validation in multiple active response scripts allows argument injection

> Attackers can inject arguments into privileged system commands via crafted log events, enabling code execution or account lockout in Wazuh.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-mvh4-g699-984j

## What is CVE-2026-54085?

CVE-2026-54085 is a high-severity command injection vulnerability in Wazuh Wazuh, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.2.0 through 4.14.6, multiple active response scripts pass attacker-influenced alert fields to privileged system commands without validating their format, allowing argument injection into tools that run as root. Five of the eight scripts that handle the srcip field, route-null.c, netsh.c, pf.c, npf.c, and ipfw.c, omit the get_ip_version() check that rejects non-IP input, and disable-account.c passes the dstuser field to passwd/chuser with only a comparison against "root". An attacker who can inject crafted log events, for example via syslog, can supply srcip or dstuser values that, when an active response rule triggers, are passed unvalidated to firewall and account-management commands such as pfctl, npfctl, ipfw, route, netsh, and passwd. This enables injecting additional command arguments, and on Windows the unquoted CreateProcess command-line concatenation in wpopenv() lets a srcip containing spaces add further arguments, while disable-account.c can be abused to lock arbitrary system accounts. This issue is fixed in version 4.14.7.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Wazuh Wazuh.

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

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

## Is CVE-2026-54085 being exploited?

There is no known exploitation of CVE-2026-54085 in the wild and no public exploit code.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54085 is a high-severity command injection vulnerability in Wazuh Wazuh, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54085 in the wild and no public exploit code.

Affected product: Wazuh 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-54085/ (Markdown: https://insights.sbomify.com/CVE-2026-54085/index.md)
```

## Sources

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

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