Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 3.9.0 until 4.14.5 and 5.0.0-beta2, the Wazuh cluster protocol in framework/wazuh/core/cluster/common.py allows an authenticated cluster node to exhaust memory on the master. The receive_str() method accepts an attacker-controlled total for InBuffer without a maximum, so a new_str command can request a multi-gigabyte bytearray and repeated requests accumulate in in_str. The divided-message path also retains flag_divided fragments under unique counters in div_msg_box without a count, aggregate-size, or expiration limit. Exploitation can disrupt agent connectivity and alert processing across the monitored environment. This issue is fixed in versions 4.14.5 and 5.0.0-beta2.
Published: 2026-08-19
Score: 4.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An authenticated cluster node can exploit Wazuh's receive_str() method by requesting an arbitrarily large bytearray, causing unbounded memory allocation on the master node. The size of the requested data directly increases memory consumption; repeated requests accumulate unbounded flag_divided fragments under unique counters in div_msg_box, which also lack size or expiration controls. Together, these weaknesses can exhaust master memory, crash the master node, and disrupt agent connectivity and alert processing across the monitored environment.

Affected Systems

Versions of Wazuh from 3.9.0 up to 4.14.5 and 5.0.0-beta2 are affected. The issue resides in framework/wazuh/core/cluster/common.py and can impact any deployment using the cluster protocol.

Risk and Exploitability

The CVSS score of 4.9 indicates a moderate severity, and the EPSS score of < 1% indicates a very low but nonzero exploitation probability, suggesting exploitation likelihood has not been quantified publicly. The vulnerability is not listed in CISA KEV, and the attack requires an authenticated cluster node to send crafted requests. If successful, a cluster node could exhaust master memory, leading to denial of service for the entire cluster.

Generated by OpenCVE AI on August 20, 2026 at 14:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Wazuh 4.14.5 or later, or 5.0.0-beta2, which contain a fixed cluster protocol implementation.
  • If upgrading is not immediately possible, isolate the vulnerable cluster node by restricting network access to the master or disabling the cluster protocol between the node and the master.
  • Monitor the master node's memory usage and restart the process if abnormal growth is detected to mitigate potential service disruption.

Generated by OpenCVE AI on August 20, 2026 at 14:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 03:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 19 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
First Time appeared Wazuh
Wazuh wazuh
Vendors & Products Wazuh
Wazuh wazuh

Wed, 19 Aug 2026 16:15:00 +0000

Type Values Removed Values Added
Description Wazuh is a free and open source platform used for threat prevention, detection, and response. From 3.9.0 until 4.14.5 and 5.0.0-beta2, the Wazuh cluster protocol in framework/wazuh/core/cluster/common.py allows an authenticated cluster node to exhaust memory on the master. The receive_str() method accepts an attacker-controlled total for InBuffer without a maximum, so a new_str command can request a multi-gigabyte bytearray and repeated requests accumulate in in_str. The divided-message path also retains flag_divided fragments under unique counters in div_msg_box without a count, aggregate-size, or expiration limit. Exploitation can disrupt agent connectivity and alert processing across the monitored environment. This issue is fixed in versions 4.14.5 and 5.0.0-beta2.
Title Wazuh: Cluster Protocol Memory Exhaustion (DoS) via unbounded receive_str allocation and div_msg_box accumulation
Weaknesses CWE-770
CWE-789
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-25T02:13:49.793Z

Reserved: 2026-05-05T16:33:55.844Z

Link: CVE-2026-44253

cve-icon Vulnrichment

Updated: 2026-08-25T02:13:44.356Z

cve-icon NVD

Status : Received

Published: 2026-08-19T16:17:10.833

Modified: 2026-08-25T03:16:54.987

Link: CVE-2026-44253

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T14:30:03Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value