Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents low real-world risk despite its network accessibility. The CVSS v3.1 score of 3.5 reflects a low severity rating driven by several mitigating factors: (1) Requires Low Privilege authentication (PR:L), eliminating unauthenticated remote attack surface; (2) Requires User Interaction (UI:R), meaning the user must perform an action for exploitation; (3) Scope is Unchanged (S:U), limiting blast radius to the authd process itself; (4) Impact is Availability only (A:L), with no Confidentiality or Integrity impact, meaning no data exfiltration or privilege escalation potential. The lack of a publicly available exploit code or CISA KEV designation further reduces exploitation likelihood. While the vulnerability is automatable in principle (heap overflows are generally not human-dependent once triggered), the authentication barrier and user interaction requirement significantly narrow the attack surface. This should be treated as a moderate-priority patch for availability-sensitive deployments rather than an emergency. |
| Exploit ScenarioDerived | An authenticated attacker with valid Wazuh credentials crafts a specially formatted authentication request or enrollment message targeting the authd daemon. When authd processes this malicious input without proper bounds checking, a heap-buffer overflow is triggered, corrupting the authd process memory and causing it to crash or become unresponsive. This results in temporary denial of authentication services for legitimate Wazuh agents attempting to enroll or renew credentials, disrupting monitoring operations until the daemon is restarted. The attack requires network access to the authd port and valid authentication credentials, making it suitable for insider threats or attackers who have compromised a Wazuh agent account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 27, 2026
Wazuh authd daemon contains a heap-buffer overflow vulnerability (CWE-125) triggered by specially crafted input from authenticated remote users, causing memory corruption and denial of service to the authentication daemon. The vulnerability affects all versions of Wazuh (CPE: cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*) and requires authenticated network access to exploit; no public exploit code or active exploitation has been confirmed at this time.
RemediationAI
Consult the Wazuh vendor security advisory (https://github.com/advisories/GHSA-grjq-p5fg-m24r) for the specific patched version and upgrade authd to the recommended release. As an interim mitigation, restrict network access to the authd service to trusted administrative hosts and networks, enforce strong authentication mechanisms (multi-factor authentication where supported), and monitor authd process logs for abnormal memory errors or crashes. Consider deploying Wazuh in a network segmentation strategy to limit the propagation of a potential denial of service condition to other infrastructure components.
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 vulnerability resides in Wazuh's authd (authentication daemon), a critical component responsible for agent authentication and enrollment in the Wazuh security monitoring platform. The root cause is classified under CWE-125 (Out-of-bounds Read), which typically indicates improper bounds checking in heap memory operations. When authd processes specially crafted authentication requests from authenticated users, a heap-buffer overflow condition is triggered, leading to memory corruption. The vulnerability is network-accessible (CVSS AV:N) but requires prior authentication (PR:L), meaning an attacker must possess valid Wazuh credentials to trigger the flaw.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Wazuh authd contains a heap-buffer overflow vulnerability that allows attackers to cause memory corruption and malformed heap data by sending specially crafted input. Attackers can exploit this vulnerability to trigger a denial of service condition, resulting in low availability impact to the authentication daemon.
Executive ViewAI
Organizations using Wazuh authd should be aware of moderate risk from CVE-2026-32984, a out-of-bounds read vulnerability rated CVSS 5.3. Exploitation could cause memory corruption or application crashes. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: enable ASLR/DEP, apply network segmentation.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-16688
GHSA-prvg-j23h-9v2j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB