CVE-2026-32984: Heap buffer overflow in wazuh-authd
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 impact on the availability of the authentication daemon.
Security readout for executives and security teams
Plain-English summary
CVE-2026-32984 is a Wazuh authd memory-safety flaw. A crafted input can corrupt heap memory and disrupt the authentication daemon, causing a denial of service. The documented impact is limited to low availability impact, not data theft or privilege escalation.
Executive priority
Handle as a moderate operational resilience issue. It can disrupt Wazuh authentication services but sources do not indicate compromise, data exposure, or active exploitation.
Technical view
The issue affects Wazuh authd/os_auth and is described as a heap-buffer overflow with CWE-125 listed. CVSS 4.0 is 5.3: network reachable, low complexity, no privileges, passive user interaction, and low vulnerable-system availability impact only.
Likely exposure
Exposure is most likely where Wazuh 3.5.0 or 4.3.10 runs authd and that service is reachable by untrusted networks or enrollment workflows. The source bundle does not prove broader version ranges.
Exploitation context
The bundle does not show active exploitation, and KEV is false. Sources describe crafted input causing memory corruption and malformed heap data, with denial of service as the stated outcome.
Researcher notes
Version evidence is narrow in the bundle. The title says heap-buffer overflow while CWE-125 is listed, so preserve both facts and avoid assuming code execution. Validate service exposure and exact Wazuh build mapping.
Mitigation direction
Check Wazuh and GitHub advisory guidance for fixed or unaffected versions.
Restrict authd exposure to trusted management networks only.
Prioritize upgrade planning for listed affected Wazuh versions.
Monitor authd crashes, restarts, and malformed enrollment attempts.
Apply vendor-recommended configuration changes if published.
Validation and detection
Inventory Wazuh manager versions and os_auth/authd usage.
Confirm whether versions 3.5.0 or 4.3.10 are deployed.
Review network reachability to authd from untrusted segments.
Check logs for authd crashes or abnormal authentication daemon restarts.
Track vendor advisories for version mapping and remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.