CVE-2026-44901

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% 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
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.4Exploit: 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-beta2, AffectedItemsWazuhResult.merge() in framework/wazuh/core/results.py trusts the sort_casting field in a cluster worker's JSON response. During a distributed API merge, attacker-controlled type names are resolved through Python builtins without an allowlist. A compromised worker can set sort_casting to exec and place Python source in affected_items, causing the master to execute the payload as root when responses from multiple nodes are merged. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.

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

Published

August 19, 2026

Last Modified

September 15, 2026

Advisory Details (5)

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

Wazuh v5.0.0 Beta 2

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

https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2
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 b29849f8abb0 (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta2 (contains commit b29849f8abb0)

https://github.com/wazuh/wazuh/commit/b29849f8abb08d78f257e6106b6111a8a1b0e621
github_pr Patch Available

Add cluster validations

Patch available: wazuh/wazuh v5.0.0-beta2 (PR #35757 merged 2026-04-28)

https://github.com/wazuh/wazuh/pull/35757
github Patch Available🟡 PoC Available

Wazuh Cluster DAPI Protocol Deserialization of Untrusted Data Remote Code Execution Vulnerability · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-8c6v-7g3w-prrq

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44901?
CVE-2026-44901 is a high 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-beta2, AffectedItemsWazuhResult.merge() in framework/wazuh/core/results.py trusts the sortcasting field in a cluster worker's JSON response. During a distributed API…
When was CVE-2026-44901 disclosed?
CVE-2026-44901 was first published in the National Vulnerability Database 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-44901 actively exploited?
CVE-2026-44901 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 49.3% of all scored CVEs.
What is the CVSS score of CVE-2026-44901?
CVE-2026-44901 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-44901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44901, 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-44901

Explore →

Is Your Infrastructure Affected by CVE-2026-44901?

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

Start Free Scan →Browse All CVEs