Skip to main content

Wazuh CVE-2026-44251

| EUVDEUVD-2026-45089 MEDIUM
Heap-based Buffer Overflow (CWE-122)
2026-07-17 GitHub_M
6.5
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain enrolled Wazuh agent credential
  2. Delivery
    Connect to manager as enrolled agent
  3. Exploit
    Send crafted underflow-triggering message
  4. Execution
    Trigger size_t underflow in msgs.c:389
  5. Persist
    Crash wazuh-remoted process
  6. Impact
    All 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

wazuh 3.0.0, < 4.14.5

Affected Packages

euvd wazuh_3_0_0 fix: 4.14.5

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

Vendor (GitHub_M) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 6.5 MEDIUM

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).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

1
Patch available
Jul 17, 2026 - 02:32 EUVD

DescriptionCVE.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

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Medium
open source SIEM/XDR with significant but not ubiquitous enterprise adoption
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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 5

More in Wazuh

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2021-44079 CRITICAL POC
9.8 Nov 22

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

CVE-2026-48024 CRITICAL POC
9.1 Aug 19

Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in version

CVE-2026-48162 CRITICAL POC
9.1 Aug 19

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

CVE-2026-61800 CRITICAL POC
9.1 Aug 27

Arbitrary file write leading to root remote code execution affects Wazuh worker nodes in clustered deployments running v

CVE-2026-25769 CRITICAL POC
9.1 Mar 17

A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achi

CVE-2025-30201 CRITICAL POC
9.1 Nov 21

Wazuh Agent before 4.13.0 on Windows can be made by an authenticated, high-privileged configuration writer to open attac

CVE-2026-44901 HIGH POC
8.4 Aug 19

Remote code execution on the Wazuh cluster master node is achievable by any attacker who controls a cluster worker node,

CVE-2026-54083 HIGH POC
8.1 Aug 27

Path traversal in Wazuh's ip-customblock active response script allows low-privileged remote attackers to create or dele

CVE-2018-19666 HIGH POC
7.8 Nov 29

The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversa

CVE-2026-44252 HIGH POC
7.7 Aug 19

Cluster key disclosure in Wazuh Manager versions 4.0.0 through 4.14.4 enables a two-stage privilege escalation: a low-pr

CVE-2026-71540 HIGH POC
7.5 Sep 24

Unauthenticated remote denial of service in the Wazuh cluster daemon (wazuh-clusterd) allows a network peer to exhaust p

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy