CVE-2026-44901
Received Received - Intake

Code Execution in Wazuh via Malicious sort_casting Parameter

Vulnerability report for CVE-2026-44901, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
wazuh wazuh From 4.0.0 (inc) to 4.14.6 (inc)
wazuh wazuh 5.0.0-beta2
wazuh wazuh 4.0.0
wazuh wazuh 4.14.6
wazuh wazuh From 4.0.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-44901 is a remote code execution vulnerability in Wazuh's Cluster DAPI Protocol affecting versions 4.0.0 to 4.14.6 and 5.0.0-beta2. The flaw exists in the AffectedItemsWazuhResult.merge() function where the sort_casting field is deserialized from JSON responses without validation. An attacker can send a crafted JSON payload with sort_casting set to exec and a malicious Python payload in affected_items. When the master node merges responses from multiple workers, it executes the payload as root via exec().

Detection Guidance

To detect this vulnerability, check if your Wazuh Manager version is between 4.0.0 and 4.14.5 or 5.0.0-beta2. Run: wazuh-control -v to check the version. Inspect logs for suspicious cluster API requests with sort_casting=exec in JSON payloads.

Impact Analysis

This vulnerability allows an attacker with control over a worker node to execute arbitrary code on the master node with root privileges. This could lead to full system compromise, unauthorized access to sensitive data, installation of malware, or disruption of services. The attack requires a compromised worker node and specific node ordering in requests.

Compliance Impact

This vulnerability could severely impact compliance with GDPR and HIPAA by enabling unauthorized access to sensitive personal or health data. A successful exploit could lead to data breaches, violating confidentiality requirements. Organizations using affected Wazuh versions may face regulatory penalties, loss of certification, and reputational damage.

Mitigation Strategies

Upgrade Wazuh Manager to version 4.14.6 or later immediately. If upgrading is not possible, restrict network access to the Wazuh cluster API and monitor for unauthorized exec calls in logs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44901. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart