SEPTEMBER 17, 2026
Live Feed
Back to database
Case File

CVE-2026-54084

MEDIUM · CVSS 5.3 EPSS 0.12% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-28 · Last synced 2026-09-17

CyberRota Analysis

AI-Generated

Wazuh agents in versions 4.0.0 through 4.14.6 are vulnerable to a denial-of-service attack during the enrollment process due to improper validation of key responses, which can lead to a NULL pointer dereference and crash the agent. Attackers can exploit this flaw by either operating a malicious enrollment manager or intercepting the enrollment flow, particularly in environments lacking a configured CA certificate. Organizations using affected versions should prioritize upgrading to version 4.14.7 to mitigate this risk.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-54084
Severity
MEDIUM
CVSS
5.3
EPSS
0.12%

Original NVD Description

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.0.0 through 4.14.6, a malicious or man-in-the-middle enrollment manager can crash a Wazuh agent during enrollment by returning a malformed key response with fewer than four fields, causing a NULL pointer dereference. The  w_enrollment_process_agent_key()  routine splits the manager-provided key into four space-separated fields but does not verify that all fields are present before passing them to validators. Because OS_StrBreak() leaves missing trailing entries as NULL and OS_IsValidName() calls strlen() on its argument without a NULL check, a response such as  OSSEC K:'1'  reaches OS_IsValidName(NULL) and terminates the agent process. Since Wazuh permits enrollment against an unverified manager when no CA certificate is configured, an attacker operating a rogue manager or intercepting the enrollment flow can deterministically crash agents, resulting in denial of service. This issue is fixed in version 4.14.7.

Related CVEs

Other vulnerabilities affecting the same vendor(s)