CVE-2026-54085

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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 14× in last 7d / 56× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-10 01:44 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-09 02:53 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-08 01:11 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-07 02:52 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-06 00:50 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-05 08:40 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-10-03 14:56 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-03 01:50 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-01 22:32 UTCEG score recompute
Show 64 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-09-30 19:53 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-30 04:23 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-09-29 12:12 UTCEG score recompute
  7. 2026-09-28 21:12 UTCEG score recompute
  8. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-09-27 18:47 UTCEG score recompute
  10. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-27 05:48 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-26 15:49 UTCEG score recompute
  14. 2026-09-25 01:48 UTCEG score recompute
  15. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-23 23:48 UTCEG score recompute
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  18. 2026-09-22 21:43 UTCEG score recompute
  19. 2026-09-22 08:43 UTCEG score recompute
  20. 2026-09-21 06:43 UTCEG score recompute
  21. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  22. 2026-09-20 04:41 UTCEG score recompute
  23. 2026-09-19 02:39 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  25. 2026-09-18 00:39 UTCEG score recompute
  26. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  27. 2026-09-16 22:38 UTCEG score recompute
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  29. 2026-09-16 09:14 UTCEG score recompute
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-09-15 10:14 UTCEG score recompute
  32. 2026-09-13 18:57 UTCEG score recompute
  33. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-12 16:57 UTCEG score recompute
  35. 2026-09-11 14:57 UTCEG score recompute
  36. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-10 12:57 UTCEG score recompute
  38. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-09 10:14 UTCEG score recompute
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-07 20:46 UTCEG score recompute
  42. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-06 18:44 UTCEG score recompute
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-05 16:43 UTCEG score recompute
  46. 2026-09-04 14:38 UTCEG score recompute
  47. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-09-02 23:38 UTCEG score recompute
  49. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-09-01 21:35 UTCEG score recompute
  51. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-09-01 08:35 UTCEG score recompute
  53. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-31 19:32 UTCEG score recompute
  55. 2026-08-31 18:34 UTCEG score recompute
  56. 2026-08-31 06:37 UTCEG score recompute
  57. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-30 04:37 UTCEG score recompute
  59. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-08-29 02:35 UTCEG score recompute
  61. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-08-28 00:30 UTCEG score recompute
  63. 2026-08-27 23:23 UTCEG score recomputeFirst assessed: 7.1 HIGH
  64. 2026-08-27 23:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54085?
CVE-2026-54085 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54085 published?
The CVE record for CVE-2026-54085 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 15, 2026; the record at its source may have been updated since.
Is CVE-2026-54085 actively exploited?
CVE-2026-54085 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54085?
CVE-2026-54085 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54085?
A fix for CVE-2026-54085 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs