CVE-2026-54084

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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
Elevated
5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: No code on recordExposed 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.0.0 through 4.14.6, a malicious or man-in-the-middle enrollment manager can crash a Wazuh agent during enrollment by returning a malformed key response with fewer than four fields, causing a NULL pointer dereference. The  w_enrollment_process_agent_key()  routine splits the manager-provided key into four space-separated fields but does not verify that all fields are present before passing them to validators. Because OS_StrBreak() leaves missing trailing entries as NULL and OS_IsValidName() calls strlen() on its argument without a NULL check, a response such as  OSSEC K:'1'  reaches OS_IsValidName(NULL) and terminates the agent process. Since Wazuh permits enrollment against an unverified manager when no CA certificate is configured, an attacker operating a rogue manager or intercepting the enrollment flow can deterministically crash agents, resulting in denial of service. This issue is fixed in version 4.14.7.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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 7dfbb4a292bc (wazuh/wazuh)

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

https://github.com/wazuh/wazuh/commit/7dfbb4a292bc6ae8e3bb4c1982f687f35216a748
GitHub advisoryMentions a patch (unverified)

Wazuh agent enrollment NULL pointer dereference via malformed manager response · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-ppc7-hj9v-vx39

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 51× 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.2% · 8th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th 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.2% · 8th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-10 05:19 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-09 02:53 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-08 01:11 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-06 19:45 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-05 18:08 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-03 14:56 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-02 07:35 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-01 05:58 UTCEG score recompute
Show 52 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-09-30 04:22 UTCEG score recompute
  3. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-09-28 21:12 UTCEG score recompute
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-09-27 17:25 UTCEG score recompute
  7. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-09-26 15:49 UTCEG score recompute
  10. 2026-09-25 11:47 UTCEG score recompute
  11. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-09-24 10:10 UTCEG score recompute
  13. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-23 08:34 UTCEG score recompute
  15. 2026-09-22 06:57 UTCEG score recompute
  16. 2026-09-21 05:21 UTCEG score recompute
  17. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-20 03:16 UTCEG score recompute
  19. 2026-09-19 01:39 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-18 00:02 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-16 21:30 UTCEG score recompute
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-09-15 08:01 UTCEG score recompute
  27. 2026-09-14 06:25 UTCEG score recompute
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-09-12 03:12 UTCEG score recompute
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-11 01:34 UTCEG score recompute
  32. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-09-09 23:57 UTCEG score recompute
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  35. 2026-09-07 11:42 UTCEG score recompute
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-09-06 09:59 UTCEG score recompute
  38. 2026-09-05 08:23 UTCEG score recompute
  39. 2026-09-03 05:06 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-09-02 03:16 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-08-30 23:52 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  46. 2026-08-29 22:15 UTCEG score recompute
  47. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  48. 2026-08-28 20:39 UTCEG score recompute
  49. 2026-08-28 19:45 UTCEG score recompute
  50. 2026-08-28 00:30 UTCEG score recompute
  51. 2026-08-27 23:23 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  52. 2026-08-27 23:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54084?
CVE-2026-54084 is a medium-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.0.0 through 4.14.6, a malicious or man-in-the-middle enrollment manager can crash a Wazuh agent during enrollment by returning a malformed key response with fewer…
When was the CVE record for CVE-2026-54084 published?
The CVE record for CVE-2026-54084 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-54084 actively exploited?
CVE-2026-54084 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54084?
CVE-2026-54084 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54084?
A fix for CVE-2026-54084 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-54084

Explore →

Is Your Infrastructure Affected by CVE-2026-54084?

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

Book a Demo →Browse All CVEs