CVE-2026-44901 wazuh CVE debrief

Who should care

Defenders and security teams using Wazuh for threat prevention, detection, and response should assess their exposure and prioritize patching or mitigating this vulnerability. This includes reviewing Wazuh version and patch level, monitoring logs for suspicious activity, and verifying the integrity of cluster worker JSON responses.

Why it matters

This vulnerability allows an attacker to execute arbitrary Python code as root, potentially compromising Wazuh master nodes and disrupting security monitoring and response capabilities. Defenders should prioritize patching or mitigating this vulnerability, especially in environments where Wazuh is used for security monitoring and response.

• Potential for arbitrary Python code execution as root
• Possible compromise of Wazuh master nodes
• Need for verification of Wazuh version and patch level
• Potential disruption of security monitoring and response capabilities

Technical summary

The `AffectedItemsWazuhResult.merge()` function in `framework/wazuh/core/results.py` does not properly validate the `sort_casting` field in cluster worker JSON responses. This allows a compromised worker to inject malicious Python code, which is then executed by the master node during distributed API merges. The issue arises from the lack of validation and sanitization of user-supplied input, allowing an attacker to execute arbitrary Python code as root. Defenders should prioritize patching or mitigating this vulnerability, especially in environments where Wazuh is used for security monitoring and response.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially in environments where Wazuh is used for security monitoring and response.

Recommended defensive actions

• Patch Wazuh to version 4.14.6 or 5.0.0-beta2 or later
• Restrict access to cluster workers to prevent manipulation of JSON responses
• Monitor for suspicious activity in Wazuh logs
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Wazuh versions from 4.0.0 to 4.14.6 and 5.0.0-beta2. The issue is fixed in versions 4.14.6 and 5.0.0-beta2. Evidence is limited to public statements from the vendor and CVE Program records. Defenders should verify Wazuh version and patch level, review logs for suspicious activity, and assess exposure in their environment.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.