Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to wazuh-authd TCP/1515
-
DeliverySend crafted enrollment V: field
-
Exploitstrncpy fills buffer without null terminator
-
Executionstrchr and strtok read beyond buffer
-
Persiststrtok writes null byte to adjacent stack
-
Impactauthd process crashes, denying enrollment
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that wazuh-authd is actively running and configured with anonymous TLS enrollment enabled on TCP port 1515 - this is the specific feature flag that exposes the vulnerable compare_wazuh_versions() code path to unauthenticated callers. The CVSS vector PR:N confirms no authentication is required prior to triggering the flaw; UI:N confirms no user interaction is needed. The key limiting factors are: (1) anonymous enrollment must be enabled - deployments requiring certificate-based agent authentication are not reachable via this path; (2) TCP/1515 must be network-accessible to the attacker - environments where this port is firewalled to trusted agent subnets have reduced exposure; (3) the impact is bounded to a null byte stack write, which in practice causes a process crash (DoS) rather than arbitrary code execution. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5 High) correctly captures a network-reachable, pre-authentication, low-complexity denial-of-service path with no confidentiality or integrity impact. The most significant limiting factor - not reflected in the raw CVSS score - is the prerequisite that anonymous TLS enrollment must be enabled on wazuh-authd; organizations that require certificate-based agent authentication or that disable the enrollment daemon are not exposed. In large-scale automated deployments (cloud auto-scaling, CI pipelines, MSSP environments), anonymous enrollment is routinely enabled, meaning the effective attack surface can be substantial even for a Wazuh operator the size of a mid-sized municipal IT team in mielec. No EPSS score was provided in the input data, so exploitation probability cannot be quantified; the absence of KEV listing and public POC reduces urgency somewhat but should not encourage complacency given how straightforward the attack path is from the published description. The null byte write outcome points strongly toward a reliable crash rather than code execution, keeping the impact bounded to availability. Overall real-world priority: high for any deployment with anonymous enrollment exposed to untrusted networks; lower for locked-down environments requiring agent certificates. |
| Exploit ScenarioDerived | An unauthenticated attacker with TCP access to port 1515 on a Wazuh manager running with anonymous enrollment enabled opens a TLS connection to wazuh-authd and sends a crafted enrollment request containing a 'V:' field of exactly nine non-null bytes. The malformed version string fills the 10-byte stack buffer without a null terminator, causing strtok() to write a null byte into adjacent stack memory and crashing the authd process. No public proof-of-concept has been identified, but the attack is directly constructible from the published description and patch diff. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 19, 2026
Stack-based buffer overflow in Wazuh's wazuh-authd enrollment daemon (versions 4.5.0 through 4.14.5 and 5.0.0-beta1) allows unauthenticated remote attackers to crash the service by sending a crafted nine-byte version string in the enrollment 'V:' field, triggering unsafe stack memory reads and a null byte write into adjacent stack frames. The vulnerable code path in compare_wazuh_versions() is reachable before authentication over TCP port 1515 when anonymous TLS enrollment is enabled, resulting in a denial of service against the agent enrollment service. No active exploitation has been confirmed (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis; vendor-released patches are available in versions 4.14.6 and 5.0.0-beta2.
RemediationAI
Upgrade to Wazuh 4.14.6 (https://github.com/wazuh/wazuh/releases/tag/v4.14.6) or 5.0.0-beta2 (https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2); both releases include the fix from PR #36059 (commit b6aac379982d6144b8da38450cbea6c8dc15be44) that adds explicit null termination after strncpy(), closing the out-of-bounds read/write path entirely. If immediate patching is not feasible, disable anonymous TLS enrollment by configuring wazuh-authd to require agent certificate authentication - this eliminates the unauthenticated attack surface but will prevent automated self-enrollment workflows, requiring manual or PKI-based agent provisioning. As a complementary network-layer control, restrict inbound TCP/1515 access to trusted agent source IP ranges via host firewall or perimeter ACLs; this does not fix the vulnerability but limits who can attempt to trigger it and reduces exposure to untrusted networks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw resides in compare_wazuh_versions() within src/shared/version_op.c, part of wazuh-authd - the Wazuh manager component that handles agent enrollment on TCP port 1515. The function declares a 10-byte stack-allocated character array (char ver1[10] / char ver2[10]) and copies the attacker-supplied version string using strncpy(ver1, version1, 9) without appending an explicit null terminator. CWE-121 (Stack-based Buffer Overflow) precisely describes the root cause: when input is exactly nine non-null bytes, the buffer is left without a null terminator, causing the immediately subsequent strchr() and strtok() calls to read beyond the ver1/ver2 boundaries into adjacent stack memory. Because strtok() writes a null byte when it finds a delimiter (or at the end of its traversal), this out-of-bounds write corrupts the adjacent stack frame, typically causing a crash of the authd process rather than controllable code execution. The fix (PR #36059, commit b6aac379) replaces the hardcoded 9-byte limit with sizeof(ver1) - 1 and appends an explicit null terminator, a canonical safe-strncpy pattern. Affected CPE: cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*.
Know when Wazuh gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Network-reachable pre-authentication path; no confidentiality or integrity impact; crash of authd yields high availability loss.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.5.0 until 4.14.6 and 5.0.0-beta2, compare_wazuh_versions() in src/shared/version_op.c copies the attacker-controlled enrollment V: field into a 10-byte stack buffer with strncpy() but does not explicitly terminate the buffer. The function is reachable before authentication through wazuh-authd on TCP port 1515 when anonymous TLS enrollment is enabled. A version string of at least nine non-null bytes can cause strchr() and strtok() to read beyond ver2 and can make strtok() write a null byte into adjacent stack memory, allowing a remote denial of service. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.
Executive ViewAI
Wazuh's agent enrollment service (affected versions 4.5.0-4.14.5 and 5.0.0-beta1) is vulnerable to remote denial-of-service attacks that can crash the service and prevent new security agents from joining the infrastructure, degrading organizational security monitoring coverage. The vulnerability is exploitable without authentication, though no public exploitation has been observed, allowing time for structured remediation. Vendor-released patches address this issue and can be deployed through standard change management processes.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl comman
Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in version
Arbitrary file read in Wazuh cluster deployments (4.0.0 through 4.14.5, and 5.0.0-beta1/beta2) lets a peer node that alr
Arbitrary file write leading to root remote code execution affects Wazuh worker nodes in clustered deployments running v
A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achi
Wazuh Agent before 4.13.0 on Windows can be made by an authenticated, high-privileged configuration writer to open attac
Remote code execution on the Wazuh cluster master node is achievable by any attacker who controls a cluster worker node,
Path traversal in Wazuh's ip-customblock active response script allows low-privileged remote attackers to create or dele
The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversa
Cluster key disclosure in Wazuh Manager versions 4.0.0 through 4.14.4 enables a two-stage privilege escalation: a low-pr
Unauthenticated remote denial of service in the Wazuh cluster daemon (wazuh-clusterd) allows a network peer to exhaust p
EUVD-2026-62574
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB