CVE-2026-28220VulnerabilityPublished 11 Aug 2026

ZDI-26-528: Wazuh Cluster DAPI Protocol Deserialization of Untrusted Data Remote Code Execution Vulnerability

Source Zero Day Initiative

Compare

Not known to be exploited.

Data as of 9 Nov 2026, 23:24 UTC

Severity

Critical

Rated Critical by Zero Day Initiative · No CVSS score from NVD or the CNA

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Wazuh has released an official update that addresses this vulnerability. Users should apply the provided security update promptly to remediate the issue. No alternative mitigations are indicated by the vendor advisory.

Description

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Wazuh. An attacker must first obtain the ability to execute low-privileged code on a worker node in order to exploit this vulnerability. The ZDI has assigned a CVSS rating of 9.9. The following CVEs are assigned: CVE-2026-28220.

Impact

An attacker who has already gained low-privileged code execution on a worker node can escalate privileges and execute arbitrary code with root permissions on the master node. This compromises the entire Wazuh cluster, potentially leading to full system compromise, data breach, and disruption of security monitoring capabilities.

Summary

CVE-2026-28220 is a critical vulnerability in Wazuh affecting the as_wazuh_object deserializer within the Cluster DAPI protocol. The flaw arises from improper validation of user-supplied data, enabling deserialization of untrusted input. An attacker with low-privileged code execution on a worker node can exploit this to execute arbitrary code as root on the master node. The vulnerability has a CVSS score of 9.9, indicating high impact on confidentiality, integrity, and availability. Wazuh has issued a security update to fix this vulnerability.

References

zerodayinitiative.com/advisories/ZDI-26-528/ (opens in a new tab)

Community reviews

Loading reviews…