CVE-2026-54085
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 14% of all known CVEs.
References
Related Vulnerabilities
Other CWE-88 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2016-10033 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-36804 | High | 8.8 | 99% | KEV | Fix |
| CVE-2026-24061 | Critical | 9.8 | 98% | KEV | Fix |
| CVE-2007-0882 | High | 10.0 | 98% | - | - |
| CVE-2018-17456 | Critical | 9.8 | 97% | - | Fix |
| CVE-2018-19518 | High | 7.5 | 95% | - | Fix |
Common questions
How do I fix CVE-2026-54085?
No published fix for CVE-2026-54085 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54085 being actively exploited?
Not that we know of. CVE-2026-54085 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.
How severe is CVE-2026-54085?
CVE-2026-54085 has a CVSS v3 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54085
Markdown
[](https://tridentstack.com/cve/CVE-2026-54085)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54085"><img src="https://tridentstack.com/cve/badge/CVE-2026-54085.svg" alt="CVE-2026-54085"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.