CVE-2026-48024

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (54th 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
9.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.8%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, cluster.unmerge_info() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled merge_type and name values in a merged synchronization archive. process_files_from_worker() in framework/wazuh/core/cluster/master.py does not adequately confine the resulting path to the declared cluster item directory. A cluster peer holding the shared Fernet key can use traversal in files_metadata.json or a merged-file header to write files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution when Wazuh services reload. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity91% × 45%
The EG Score, 9.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.8%
EPSS %ILE
54th
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 19, 2026

Last Modified

September 15, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-gh4h-fx78-q8xc
GitHub release Patch Available

Wazuh v5.0.0 Beta 3

Patch available: wazuh/wazuh v5.0.0-beta3 (pre-release)

https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3
GitHub release Patch Available

Wazuh v4.14.6

Patch available: wazuh/wazuh v4.14.6

https://github.com/wazuh/wazuh/releases/tag/v4.14.6
GitHub pull request Patch Available

Improve cluster merged file parameter validation

Patch available: wazuh/wazuh v5.0.0-beta3 (PR #36204 merged 2026-05-20)

https://github.com/wazuh/wazuh/pull/36204
GitHub commit Patch Available

commit 88fc89fdfb1b (wazuh/wazuh)

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

https://github.com/wazuh/wazuh/commit/88fc89fdfb1bf37b9d826e9c281a3d22655733de

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48024?
CVE-2026-48024 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, cluster.unmergeinfo() in framework/wazuh/core/cluster/cluster.py constructs paths from peer-controlled mergetype and name values in a merged synchronization…
When was the CVE record for CVE-2026-48024 published?
The CVE record for CVE-2026-48024 was published on August 19, 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-48024 actively exploited?
CVE-2026-48024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48024?
CVE-2026-48024 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48024?
A fix for CVE-2026-48024 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-48024

Explore →

Is Your Infrastructure Affected by CVE-2026-48024?

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

Book a Demo →Browse All CVEs