CVE-2026-48024

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% 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
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
57(Track*)
EG Risk 57/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
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

Advisory Details (5)

Auto-updated Aug 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

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_pr 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 12× in last 7d / 23× 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 03:22 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 01:55 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 16:25 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:58 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 17:41 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 16:12 UTCEG score recompute
  12. 2026-08-24 11:55 UTCEG score recompute
  13. 2026-08-23 02:00 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 00:37 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 20:23 UTCEG score recompute
  18. 2026-08-21 19:44 UTCEG score recompute
  19. 2026-08-20 23:00 UTCEG score recompute
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:23 UTCEG score recompute
  22. 2026-08-19 16:22 UTCEG score recompute
  23. 2026-08-19 16:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-48024?
CVE-2026-48024 is a critical vulnerability 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 CVE-2026-48024 disclosed?
CVE-2026-48024 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48024 actively exploited?
CVE-2026-48024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.2% of all scored CVEs.
What is the CVSS score of CVE-2026-48024?
CVE-2026-48024 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48024, 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-48024

Explore →

Is Your Infrastructure Affected by CVE-2026-48024?

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