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.5%, top 62% 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
Trending — 3 sources updated this week
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%CVSS: 9.1Exploit: None knownExposed: 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.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.1(medium)
EG Risk
41(Track)
EG Risk 41/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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
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_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
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 Patch Available🟡 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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-25 15:46 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 17:02 UTCEG score recompute
  4. 2026-08-24 12:28 UTCEG score recompute
  5. 2026-08-23 02:32 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 00:10 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 01:33 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 19:20 UTCEG score recompute
  12. 2026-08-19 18:23 UTCEG score recompute
  13. 2026-08-19 17:23 UTCEG score recompute
  14. 2026-08-19 16:22 UTCEG score recompute
  15. 2026-08-19 16:22 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database on August 19, 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% probability of exploitation in the next 30 days, which ranks it in the top 62.0% of all scored CVEs.
What is the CVSS score of CVE-2026-49441?
CVE-2026-49441 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-49441?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49441, 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-49441

Explore →

Is Your Infrastructure Affected by CVE-2026-49441?

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

Start Free Scan →Browse All CVEs