Wazuh (< 4.14.3) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/wazuh--4.14.3/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 28 Aug 2026 19:17:51 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgWazuh Cluster Mode Insecure Deserialization Vulnerability (CVE-2026-25769)https://feed.craftedsignal.io/briefs/2026-08-wazuh-rce/Fri, 28 Aug 2026 19:17:51 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-wazuh-rce/An insecure deserialization vulnerability in Wazuh cluster communication allows a compromised worker node to achieve remote code execution as root on the master node.CVE-2026-25769 is a critical insecure deserialization vulnerability affecting the cluster communication mechanism in Wazuh versions prior to 4.14.3. The flaw resides in how the Wazuh master node processes serialized data received from worker nodes within the cluster architecture. If an attacker successfully compromises a single worker node, they can leverage this vulnerability to send maliciously crafted serialized objects to the master node. Upon deserialization, these objects facilitate arbitrary command execution with root privileges on the master node. Given the high CVSS score of 9.1, this vulnerability poses a severe risk to the integrity of the entire security monitoring infrastructure, as a compromise of a worker node leads to a full takeover of the central management server.

Impact

Successful exploitation allows for full system compromise of the Wazuh master node with root-level access. This results in the complete loss of confidentiality, integrity, and availability for the security monitoring platform, potentially enabling attackers to disable detection capabilities, exfiltrate security logs, or pivot further into the internal network.

Recommendation

Prioritized actions for security operations and IT teams:

  • Upgrade all Wazuh instances in cluster configurations to version 4.14.3 or later immediately to patch CVE-2026-25769.
  • Restrict network access to the Wazuh cluster communication ports strictly to authorized worker nodes using host-based firewalls or network access control lists.
  • Audit existing Wazuh worker nodes for signs of prior compromise, as a compromised worker is the prerequisite for exploiting this vulnerability.
  • Review cluster communication logs for anomalies in traffic patterns or unexpected payload sizes originating from worker nodes.
]]>highadvisoryvulnerabilityrcewazuh