CVE-2026-54084 wazuh CVE debrief

Who should care

Defenders responsible for Wazuh agent deployment and security should assess exposure and prioritize upgrading to version 4.14.7 to prevent denial of service via agent crashes and potential man-in-the-middle attacks on enrollment flows. They should also verify agent versions and implement additional security measures to prevent exploitation.

Why it matters

Defenders should care about CVE-2026-54084 because it allows a malicious enrollment manager to crash Wazuh agents, resulting in denial of service. The issue is fixed in version 4.14.7, and defenders should prioritize verifying agent versions and upgrading if necessary.

• Denial of service via agent crashes
• Potential for man-in-the-middle attacks on enrollment flows
• Need for verification of Wazuh agent versions and remediation

Technical summary

The w_enrollment_process_agent_key() routine in Wazuh splits the manager-provided key into four space-separated fields but does not verify that all fields are present before passing them to validators. This causes a NULL pointer dereference when a response with fewer than four fields is received. The issue is triggered when a malicious or man-in-the-middle enrollment manager returns a malformed key response. Wazuh permits enrollment against an unverified manager when no CA certificate is configured, allowing an attacker operating a rogue manager or intercepting the enrollment flow to deterministically crash agents, resulting in denial of service.

Defensive priority

Defenders should prioritize verifying Wazuh agent versions and upgrading to 4.14.7 if necessary.

Recommended defensive actions

• Verify Wazuh agent versions and upgrade to 4.14.7 if necessary
• Monitor enrollment flows for suspicious activity
• Implement additional security measures to prevent man-in-the-middle attacks
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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

Evidence notes

The vulnerability is caused by a NULL pointer dereference in the w_enrollment_process_agent_key() routine. The issue is triggered when a malicious or man-in-the-middle enrollment manager returns a malformed key response with fewer than four fields.

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.