Home › Intelligence › Brief
VULNERABILITY BRIEF 🔴 Critical Vulnerability

Critical RCE in Wazuh DAPI Protocol (CVE-2026-44901) Enables Remote Code Execution on Cluster Master

Wazuh disclosed a CVE‑2026‑44901 deserialization flaw that lets a network‑adjacent attacker execute arbitrary code as root on the master node of a Wazuh cluster. The vulnerability scores 9.9 on CVSS, making it a top‑priority patch for any organization relying on Wazuh for security monitoring. From a compliance perspective, the issue highlights the need for continuous configuration control and audit‑ready evidence of patch management.

Verisq™ Intelligence · 📅 August 12, 2026 · 📰 zerodayinitiative.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
zerodayinitiative.com

Critical RCE in Wazuh DAPI Protocol (CVE‑2026‑44901) Enables Remote Code Execution on Cluster Master

What It Is — A deserialization flaw in the sort_casting field of Wazuh’s DAPI protocol allows an attacker who can run low‑privileged code on a worker node to execute arbitrary commands as root on the master node.

Exploitability — CVSS 9.9 (Critical). Network‑adjacent attacker, low‑complexity, no user interaction required. No public exploit code released, but the vulnerability is fully disclosed and a patch is available.

Affected Products — Wazuh (all versions prior to the August 2026 security update).

Why It Matters for Compliance & Audit Readiness

  • Control‑mapping gaps: The flaw bypasses expected segregation of duties between worker and master nodes, a key SOC 2 CC6.1 (Logical Access) control.
  • Continuous evidence: Demonstrating that you have an up‑to‑date patch management process and automated validation of configuration drift is essential audit evidence.
  • Trust for customers: Enterprise buyers increasingly require proof that security tooling itself is hardened; a vulnerable SIEM can invalidate your own monitoring controls.

Recommended Actions

  1. Apply the Wazuh security update (GHSA‑8c6v‑7g3w‑prrq) immediately across all clusters.
  2. Verify that the sort_casting field is no longer accepted for untrusted input by running the vendor‑provided test script.
  3. Update your SOC 2 control inventory to map “Secure Configuration Management” (CC6.2) to the patch‑management process and capture the patch‑install logs as continuous compliance evidence.
  4. Enable automated configuration drift detection on the master node and integrate findings into your audit‑ready dashboard.

Source: Zero Day Initiative advisory ZDI‑26‑527

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-527/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →