CVE-2026-74044 Wazuh CVE debrief

Who should care

Defenders responsible for Wazuh installations, cluster management, and directory security should assess exposure and implement compensating controls. This includes verifying Wazuh installations for exposure, assessing the validity of cluster Fernet keys, and restricting access to cluster peers. Additionally, defenders should prioritize monitoring and logging to detect potential exploitation attempts and implement necessary controls to prevent directory in

Why it matters

CVE-2026-74044 is a path traversal vulnerability in Wazuh that allows authenticated cluster peers to delete arbitrary directory contents. Defenders should prioritize verifying Wazuh installations, assessing cluster Fernet key validity, and restricting access to cluster peers.

• Verification of Wazuh installations for exposure is required to prevent potential directory deletions.
• Restricting access to cluster peers and validating cluster Fernet keys can help mitigate the vulnerability.
• Implementing monitoring and logging to detect potential exploitation attempts is necessary.
• Further verification of affected versions and potential impact is required to ensure comprehensive mitigation.

Technical summary

The vulnerability is caused by a lack of validation in the cluster hello payload, allowing attackers to craft a malicious node name and trigger the master's peer cleanup routine to remove arbitrary directories. This path traversal vulnerability in Wazuh 4.0.0 before 4.14.6 allows authenticated cluster peers to delete arbitrary directory contents. Attackers holding a valid cluster Fernet key can exploit this vulnerability by supplying a traversal-shaped node name in the cluster hello payload without validation, leading to potential directory deletions within the Wazuh installation path writable by the wazuh user.

Defensive priority

Defenders should prioritize verifying Wazuh installations for exposure, assessing the validity of cluster Fernet keys, and restricting access to cluster peers.

Recommended defensive actions

• Verify Wazuh installations for exposure by checking the version and configuration.
• Assess the validity of cluster Fernet keys and restrict access to cluster peers.
• Implement compensating controls to monitor and limit directory deletions within the Wazuh installation path.
• Review 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.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected versions and potential impact require further verification. Defenders should verify Wazuh installations, assess cluster Fernet key validity, and restrict access to cluster peers. Evidence is limited, and further review of affected versions and potential impact is necessary.

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.