CVE-2026-54085

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit b7f3a5e59000 (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta3 (contains commit b7f3a5e59000)

https://github.com/wazuh/wazuh/commit/b7f3a5e59000e4cdef75f397f1107ae3e1c186a9
github Patch Available

Missing input validation in multiple active response scripts allows argument injection · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-mvh4-g699-984j

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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.

  1. 2026-09-19 02:39 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:39 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 22:38 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 09:14 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 10:14 UTCEG score recompute
  10. 2026-09-13 18:57 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 16:57 UTCEG score recompute
  13. 2026-09-11 14:57 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 12:57 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-09 10:14 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 20:46 UTCEG score recompute
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 18:44 UTCEG score recompute
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 16:43 UTCEG score recompute
  24. 2026-09-04 14:38 UTCEG score recompute
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 17 more
  1. 2026-09-02 23:38 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 21:35 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 08:35 UTCEG score recompute
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-31 19:32 UTCEG score recompute
  8. 2026-08-31 18:34 UTCEG score recompute
  9. 2026-08-31 06:37 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 04:37 UTCEG score recompute
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 02:35 UTCEG score recompute
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 00:30 UTCEG score recompute
  16. 2026-08-27 23:23 UTCEG score recompute
  17. 2026-08-27 23:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54085?
CVE-2026-54085 is a high vulnerability published on August 27, 2026. 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…
When was CVE-2026-54085 disclosed?
CVE-2026-54085 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54085 actively exploited?
CVE-2026-54085 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54085?
CVE-2026-54085 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-54085?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54085, 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-54085

Explore →

Is Your Infrastructure Affected by CVE-2026-54085?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.