Wazuh
CVE-2026-34150
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach manager authd/remoted ports
-
DeliveryEnroll password-less for agent key
-
ExploitConnect to remoted via agent protocol
-
ExecutionInject rootcheck event over 30 bytes
-
PersistOverflow sprintf buffer in analysisd
-
ImpactCrash wazuh-analysisd, halt alert processing
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 | Exploitation requires network reachability to the Wazuh manager's remoted (agent protocol, default TCP 1514) and authd (enrollment, default TCP 1515) services, plus the password-less agent enrollment that is enabled in the official wazuh/wazuh-docker default configuration - that default is the exact precondition, letting an unauthenticated attacker obtain a valid agent ID and key without credentials. The concrete trigger is a rootcheck event containing a {key: value} pattern longer than 30 bytes, which overflows the fixed 30-byte sprintf buffer in W_JSON_ParseRootcheck. What LIMITS exploitation: deployments that have replaced the default by enforcing an enrollment password (use_password) or certificate-based authd authentication, or that firewall remoted/authd to trusted agent subnets, remove the unauthenticated self-enrollment path and block the documented attack; only Wazuh manager versions 1.0.0 through 4.14.4 are affected. |
| Impact | The signals are internally consistent and point to a genuine, easily reachable availability risk rather than an inflated high-CVSS finding. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) reflects unauthenticated network exploitation with low complexity and no user interaction, and the description confirms this is realistic against the default Docker configuration because authd accepts password-less enrollment out of the box. Impact is confined to availability (C:N/I:N) - no data theft or code execution is claimed - but the availability loss is severe and stealthy: alert processing stops while the API and dashboard keep showing stale data, so defenders may not notice the SIEM has gone blind. No EPSS score, KEV entry, POC, or SSVC decision data was provided, so exploitation likelihood cannot be quantified; the absence of KEV/POC suggests it is not yet weaponized, but the low attack complexity and default-config reachability make it a high-priority patch for any manager exposed to an untrusted agent network. |
| Exploit ScenarioDerived | An attacker who can reach a default Wazuh Docker manager enrolls with authd without a password, obtaining a valid agent ID and encryption key. Using those credentials over the Wazuh agent protocol to remoted, the attacker injects a rootcheck event whose {key: value} pattern exceeds 30 bytes, triggering the sprintf overflow that crashes wazuh-analysisd. Alert processing halts silently while the dashboard keeps showing stale data; no public exploit code is currently identified, but the steps are low-complexity and require no authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 17, 2026
Denial of service in Wazuh's analysis engine (wazuh-analysisd) lets an unauthenticated remote attacker permanently halt SIEM alert processing on Wazuh manager versions 1.0.0 through 4.14.4. Because the official wazuh/wazuh-docker deployment ships with password-less agent enrollment enabled by default, an attacker can register as an agent and send a crafted rootcheck event that overflows a fixed 30-byte heap buffer, crashing the daemon while the dashboard and API keep showing stale data - silently blinding the SIEM. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
Vendor-released patch: 4.14.5 - upgrade the Wazuh manager to 4.14.5 or later, which corrects the W_JSON_ParseRootcheck buffer handling; for containerized installs, pull the updated wazuh/wazuh-docker image built on 4.14.5 and redeploy. Where immediate patching is not possible, harden agent enrollment to remove the default password-less path by configuring authd to require a shared enrollment password (use_password) or client-certificate authentication, so attackers cannot self-register and obtain a valid key - the trade-off is added enrollment friction for legitimate agents. Additionally restrict network access to the remoted service (default TCP 1514) and authd (default TCP 1515) to trusted agent subnets via firewall rules, noting this does not stop a malicious host already inside the agent network. See the vendor advisory GHSA-rvr9-89q8-w883 (https://github.com/wazuh/wazuh/security/advisories/GHSA-rvr9-89q8-w883) for authoritative guidance.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Wazuh is an open-source security platform (SIEM/XDR) whose manager pipeline ingests agent telemetry through the remoted service and processes it in wazuh-analysisd, the correlation and alerting engine. The flaw (CWE-122, heap-based buffer overflow) resides in W_JSON_ParseRootcheck, which parses rootcheck events formatted as {key: value} pairs. The parser copies parsed content into a statically sized 30-byte buffer using sprintf without bounds checking, so any key/value pattern longer than 30 bytes overruns the heap allocation and corrupts adjacent memory. Per the version data in the advisory, all releases from 1.0.0 up to but not including 4.14.5 are affected in the manager component that handles the Wazuh agent protocol over remoted.
Know when Docker 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
Default-config password-less enrollment enables unauthenticated network exploitation (AV:N/PR:N) at low complexity; impact is a daemon crash, so availability only (A:H, C:N/I:N).
Primary rating from Vendor (github).
CVSS VectorVendor: github
DescriptionCVE.org
Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 1.0.0 and above, prior to 4.14.5, a heap buffer overflow in wazuh-analysisd allows an unauthenticated remote attacker to crash the Wazuh manager's analysis engine, causing complete loss of SIEM alert processing. The attack exploits the default configuration shipped in the official wazuh/wazuh-docker deployment with default configuration. An attacker can enroll with authd without a password to obtain a valid agent ID and encryption key, connect to remoted over the Wazuh agent protocol, and inject rootcheck events containing {key: value} patterns longer than 30 bytes that trigger a sprintf overflow of a 30-byte buffer in W_JSON_ParseRootcheck, corrupting the heap and crashing wazuh-analysisd so that all alert processing silently stops while the dashboard and API keep showing stale data.
Articles & Coverage 1
Executive ViewAI
Wazuh analysis engine (wazuh-analysisd) versions 1.0.0 through 4.14.4 face an unauthenticated remote denial-of-service vulnerability that silently halts all SIEM alert processing while the dashboard continues displaying stale data, creating undetected security blindness. Attackers can exploit default password-less agent enrollment to inject a malicious rootcheck event that crashes the analysis daemon, leaving organizations unaware they have lost real-time threat visibility. This affects all deployments using standard Docker configurations and creates material risk to incident detection, threat response, and regulatory compliance.
Disable password-less enrollment (auth_pass_only: true) and enforce certificate-based or PSK agent authentication. Implement strict firewall rules limiting manager agent ports (1514-1515) to authorized agent IP ranges. Deploy automated alerting on wazuh-analysisd process state changes and failed restarts. Establish daily manual validation that alert processing is functioning via test security events sent to manager. Monitor rootcheck submission rates for anomalies indicating exploitation attempts. These controls significantly reduce attack surface but do not prevent exploitation by a compromise agent-no interim control fully eliminates risk until patches are available.
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.
Affected Products (CPE)CVE.org
Related Vulnerabilities in Wazuh Memory Safety and Access Control Vulnerabilities
View all 5An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB