Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain enrolled Wazuh agent credential
-
DeliveryConnect to manager as enrolled agent
-
ExploitSend crafted underflow-triggering message
-
ExecutionTrigger size_t underflow in msgs.c:389
-
PersistCrash wazuh-remoted process
-
ImpactAll agents disconnected, monitoring blind spot achieved
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap 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 | The attacker must possess a valid Wazuh agent enrollment credential - either by controlling a legitimately enrolled agent or by stealing an agent key (CVSS PR:L confirms low-privilege enrolled-agent access is required; unauthenticated remote attackers cannot trigger this). The manager must be running Wazuh 3.0.0 through 4.14.4. No non-default configuration is required; the underflow exists in the standard agent-manager message processing path that is active in all default deployments. Exploitation is limited by the enrolled-agent requirement: external attackers without access to an enrolled agent or its credentials cannot reach the vulnerable code path. Post-crash, the wazuh-remoted service may restart automatically (depending on deployment configuration), potentially allowing repeated triggering to maintain a persistent DoS condition. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H scores 6.5, which appropriately reflects the primary availability impact: a network-accessible crash with minimal complexity requiring only enrolled-agent credentials. The S:U (scope unchanged) and C:N/I:N ratings are conservative given the secondary heap corruption path; if that path proves exploitable for code execution, integrity and confidentiality scores would need revision upward. No EPSS score was provided in the input data, making probabilistic exploitation forecasting impossible from this dataset. The absence of a KEV listing and lack of known public POC suggest exploitation has not been observed at scale, but the low barrier - any single enrolled agent, legitimate or compromised, can trigger the crash - means the attack is accessible to insider threats or attackers who have compromised one endpoint in a monitored estate. The multiplier effect (one agent crash kills visibility for all agents) elevates real-world priority above what the 6.5 base score alone implies for Wazuh-dependent security operations. |
| Exploit ScenarioDerived | An attacker who has compromised a single Wazuh-monitored endpoint - or who has exfiltrated an agent enrollment key - sends a crafted message to the Wazuh manager that triggers the size_t underflow in msgs.c:389, crashing wazuh-remoted. All other agents immediately lose connectivity to the manager, creating a monitoring blackout across the entire Wazuh deployment that the attacker can exploit to conduct further activity undetected. If the secondary heap corruption path is exploitable, the attacker may additionally achieve code execution on the manager itself, escalating from DoS to full manager compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 17, 2026
Remote denial-of-service and potential heap corruption in the Wazuh manager's wazuh-remoted daemon allows any enrolled agent to crash the manager's agent-communication process, instantly severing all agent connections across the entire deployment. Affected versions span 3.0.0 through 4.14.4; a secondary code path triggered by the same underflow may permit heap memory write primitives beyond pure DoS. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog, but the low exploitation barrier - any enrolled agent suffices - makes it a meaningful insider or supply-chain risk for Wazuh-dependent SOC environments.
RemediationAI
Upgrade Wazuh manager to version 4.14.5, which contains the official fix per vendor advisory GHSA-jv5r-5p7c-g9fq at https://github.com/wazuh/wazuh/security/advisories/GHSA-jv5r-5p7c-g9fq. Prior to patching, the most effective compensating control is to audit and minimize the enrolled agent population - revoke credentials for any agent that is decommissioned or untrusted, since the attack requires an enrolled agent identity. Network segmentation that enforces agent-to-manager traffic only from known, managed IP ranges reduces exposure to external compromise of agent keys but does not protect against insider or already-compromised endpoint scenarios. Monitoring wazuh-remoted process health and alerting on unexpected restarts can provide early detection of exploitation attempts, though this monitoring will itself be disrupted during an active attack.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect resides in os_crypto/shared/msgs.c at line 389 within the Wazuh manager codebase, classified as CWE-122 (Heap-based Buffer Overflow). The root cause is a size_t integer underflow: because size_t is an unsigned type, subtracting a larger value from a smaller one wraps around to a very large integer, which is then used as a memory allocation or copy size, corrupting heap state. The affected process, wazuh-remoted, is the single daemon that brokers all agent-to-manager communications; its crash therefore atomically disconnects every enrolled agent. CPE cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* confirms the scope covers all Wazuh releases from 3.0.0 onward until the fix in 4.14.5. The secondary code path reaching the same underflow is described by the vendor as potentially enabling heap memory corruption, which could in theory support a code-execution primitive, though this is not yet independently confirmed.
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:L/UI:N/S:U/C:N/I:N/A:H
Agent communicates over network (AV:N), enrollment credential suffices as low privilege (PR:L), and wazuh-remoted crash fully eliminates agent visibility for the entire deployment (A:H).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 3.0.0 and above, prior to 4.14.5, a size_t integer underflow in os_crypto/shared/msgs.c:389 allows any enrolled Wazuh agent to crash the wazuh-remoted process on the manager, immediately disconnecting all agents from the manager. A second code path reached by the same underflow may allow heap memory corruption. This issue has been fixed in version 4.14.5.
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 heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
Related Vulnerabilities in Wazuh Memory Safety and Access Control Vulnerabilities
View all 5Wazuh 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-45089
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB