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 86% 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
Trending — 3 sources updated this week
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
37(Track)
EG Risk 37/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 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 7× in last 7d / 7× 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-08-30 04:37 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 02:35 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 00:30 UTCEG score recompute
  6. 2026-08-27 23:23 UTCEG score recompute
  7. 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 August 28, 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 85.7% 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.

Start Free Scan →Browse All CVEs