Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCompromise Wazuh worker node
-
ExploitSend malicious serialized object to master
-
ExecutionDeserialize untrusted data
-
ImpactExecute arbitrary code as root on master
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Wazuh versions 4.0.0–4.14.2 with cluster mode (master/worker architecture) enabled. Attacker requires compromised worker node access (gained through initial access, insider threat, or supply chain attack). No victim interaction needed. Enables RCE on master node with root privileges. |
| Impact | This vulnerability presents an extremely high real-world risk despite requiring high privileges (compromised worker node) as indicated by the CVSS vector (AV:N/AC:L/PR:H). The 9.1 CVSS score accurately reflects the severity given the scope change (S:C) and full CIA impact. While EPSS data is not available and it's not listed in CISA KEV, the public availability of proof-of-concept materials significantly increases exploitation likelihood. The attack complexity is low once initial worker access is obtained, making this a priority patch for any organization running Wazuh clusters, as lateral movement from worker to master with root privileges represents a catastrophic security failure. |
| Exploit ScenarioDerived | An attacker first gains access to a Wazuh worker node through phishing, supply chain compromise, or exploiting another vulnerability, then sends specially crafted serialized objects to the master node through the cluster communication channel. The master node deserializes these malicious objects without validation, executing arbitrary code with root privileges and giving the attacker complete control over the entire Wazuh infrastructure. Proof-of-concept code is publicly available, making this attack scenario readily implementable by motivated attackers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 17, 2026
A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achieve remote code execution with root privileges on the master node. The vulnerability affects Wazuh versions 4.0.0 through 4.14.2 and poses severe risk to organizations using Wazuh in distributed deployments, as compromise of any single worker node can lead to full cluster takeover. While no active exploitation has been reported (not in KEV), proof-of-concept materials are publicly available via the Google Drive link in the advisory.
RemediationAI
Immediately upgrade all Wazuh cluster deployments to version 4.14.3 or later, which contains the security fix for this deserialization vulnerability. Until patching is complete, implement network segmentation between worker and master nodes, monitor for suspicious cluster communication patterns, and review worker node access controls to prevent initial compromise. Additional technical details and proof-of-concept information can be found at https://drive.google.com/drive/folders/1WlkKNmHexz8212OVED9O6M_3pI8b6qNI?usp=sharing, though accessing this should be limited to security teams for assessment purposes.
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 stems from unsafe deserialization of untrusted data (CWE-502) in Wazuh's cluster communication protocol between master and worker nodes. Wazuh (CPE: cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*) is an open-source security monitoring platform that uses a master-worker architecture in cluster mode for distributed threat detection and response. The deserialization flaw allows malicious payloads sent from a compromised worker node to be executed on the master node without proper validation, a classic example of trusting internal network communications without verification.
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:H/UI:N/S:C/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
4DescriptionGitHub Advisory
Wazuh is a free and open source platform used for threat prevention, detection, and response. Versions 4.0.0 through 4.14.2 have a Remote Code Execution (RCE) vulnerability due to Deserialization of Untrusted Data). All Wazuh deployments using cluster mode (master/worker architecture) and any organization with a compromised worker node (e.g., through initial access, insider threat, or supply chain attack) are impacted. An attacker who gains access to a worker node (through any means) can achieve full RCE on the master node with root privileges. Version 4.14.3 fixes the issue.
Articles & Coverage 3
Executive ViewAI
CVE-2026-25769 is a critical deserialization vulnerability in Wazuh cluster deployments that enables attackers who compromise any worker node to execute code as root on the master node, potentially causing complete security infrastructure failure. Organizations running Wazuh 4.0.0-4.14.2 in distributed configurations face immediate risk of cluster-wide compromise and loss of security visibility across their entire estate.
Apply vendor patch. If immediate patching is not feasible: (1) restrict network access to worker nodes using firewall rules to prevent lateral movement from compromised nodes to master nodes; (2) implement enhanced monitoring and alerting on cluster communication channels for anomalous deserialization activity; (3) increase monitoring frequency on master node process execution and privilege escalation attempts; (4) disable cluster mode if not operationally critical and migrate to standalone architecture temporarily.
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
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in Wazuh Platform Remote Code Execution
View all 3Wazuh 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
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
Arbitrary file deletion on a Wazuh manager via the cluster synchronization protocol allows a cluster-authenticated attac
EUVD-2026-12595
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB