CVE-2026-54083

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (45th 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
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.6%CVSS: 8.1Exploit: 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. The  ip-customblock  active response script contains a path traversal vulnerability that lets an attacker create or delete arbitrary files on the filesystem as root. The script builds a file path by concatenating the  srcip  field taken from alert JSON directly onto the fixed  /ipblock/  base directory, without validating that the value is a well-formed IP address. Because the extraction routine returns the raw string unchecked, an attacker who can trigger alert-matching log events with a crafted  srcip  containing  ../  sequences can escape the base directory. The block action opens the resulting path in append mode, creating an empty file at an arbitrary location, while the unblock action passes it to remove(), deleting an arbitrary file; since the active response daemon runs as root, this includes sensitive files such as system credentials and Wazuh configuration. Unlike the sibling scripts host-deny.c, default-firewall-drop.c, and firewalld-drop.c, which reject non-IP input via get_ip_version(), ip-customblock.c omits this validation. This issue is fixed in version 4.14.7.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
The EG Score, 8.1 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 e6ef99025b2c (wazuh/wazuh)

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

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

Path traversal in ip-customblock active response allows arbitrary file creation and deletion · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-m4mf-qmhf-8vj6

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54083?
CVE-2026-54083 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. The ip-customblock active response script contains a path traversal vulnerability that lets an attacker create or delete arbitrary files on the filesystem as root. The script…
When was the CVE record for CVE-2026-54083 published?
The CVE record for CVE-2026-54083 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-54083 actively exploited?
CVE-2026-54083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54083?
CVE-2026-54083 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54083?
A fix for CVE-2026-54083 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-54083

Explore →

Is Your Infrastructure Affected by CVE-2026-54083?

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

Book a Demo →Browse All CVEs