CVE-2026-49441

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.8% (54th percentile of EPSS-scored CVEs). 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.1Exploit: None knownExposed 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.3.0 until 4.14.6 and 5.0.0-beta3, the non-merged branch of process_files_from_worker() in framework/wazuh/core/cluster/master.py trusts a peer-controlled file_path key from files_metadata.json. The destination is joined to WAZUH_PATH without proving that it remains inside the directory selected by cluster_item_key. A cluster peer holding the shared Fernet key can upload a crafted extra-valid archive and overwrite security-sensitive files such as /var/ossec/etc/ossec.conf. Replacing ossec.conf can configure root-executed commands and lead to code execution after a service 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
41
EG Risk 41/100CISA SSVC

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%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 15, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

peer-controlled metadata key in process_files_from_worker non-merged branch allows arbitrary file write under WAZUH_PATH on Wazuh manager · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-3v57-hgvj-3vj2
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

Cluster file processing parameter validation

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

https://github.com/wazuh/wazuh/pull/36296
github_commit Patch Available

commit 7f13682cf5f0 (wazuh/wazuh)

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

https://github.com/wazuh/wazuh/commit/7f13682cf5f01f69452f723a608ab2d89cfb2133

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49441?
CVE-2026-49441 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.3.0 until 4.14.6 and 5.0.0-beta3, the non-merged branch of processfilesfromworker() in framework/wazuh/core/cluster/master.py trusts a peer-controlled filepath key from filesmetadata.json. The…
When was CVE-2026-49441 disclosed?
CVE-2026-49441 was first published on August 19, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49441 actively exploited?
CVE-2026-49441 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-49441?
CVE-2026-49441 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-49441?
A fix for CVE-2026-49441 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-49441

Explore →

Is Your Infrastructure Affected by CVE-2026-49441?

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

Book a Demo →Browse All CVEs