Cloudanix VulnDB

CVE-2026-54084

Medium · 5.3

CVSS

5.3

EPSS

0.2%

Published

Aug 28, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A flaw in Wazuh lets a fake security server send bad data that crashes the protection software on computers it watches, briefly leaving those systems without monitoring.

Exploit Available
Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Moderate
Impact
Denial Of Service
Component
Application
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Malformed enrollment key response with fewer than four space-separated fields triggers NULL pointer dereference in w_enrollment_process_agent_key when OS_StrBreak leaves trailing entries as NULL and OS_IsValidName calls strlen on a NULL argument, crashing the agent process.

Why it matters to the business

Successful exploitation produces denial of service against Wazuh agents, temporarily disabling endpoint security monitoring and XDR collection until agents are restarted or re-enrolled.

How an attack unfolds

An attacker positions a rogue manager or performs a man-in-the-middle attack on the enrollment channel; when an agent initiates enrollment without CA verification, the attacker returns a truncated key string such as 'OSSEC K:\'1\''; the agent parses it, hits the NULL dereference, and terminates.

How to fix it

Upgrade all Wazuh agents and managers to version 4.14.7 or later; enable CA certificate validation for enrollment where possible to reduce exposure to untrusted managers.

How to confirm the fix worked

Confirm installed version is 4.14.7 or newer; review enrollment configuration for presence of CA certificates; test enrollment against a manager returning truncated keys to verify crash no longer occurs.

Typical attack path

  1. Position rogue enrollment manager or intercept enrollment traffic
  2. Wait for or trigger agent enrollment request
  3. Return key response containing fewer than four fields
  4. Agent crashes via NULL dereference in key validation

How to detect it

Review Wazuh agent logs for enrollment key parsing errors or unexpected process terminations around enrollment timestamps; correlate with network captures showing short key responses from enrollment endpoints.

What your security team should do

  • Prioritize upgrade of all agents to 4.14.7 within maintenance windows
  • Enable CA-based enrollment verification to prevent rogue manager acceptance
  • Monitor agent restart rates and enrollment failure logs for anomalies

The record

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.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities