CVE-2026-44253: Wazuh is a free and open source platform used for threat prevention, detection, and response. From 3.9.0 until 4.14.5…
CVE-2026-44253 · Severity: medium · CVSS 4.9 · Published 2026-08-19
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.
No. Junglewise Threat Intelligence has no report of CVE-2026-44253 being exploited in the wild.
How severe is CVE-2026-44253?
Medium severity, with a CVSS score of 4.9, published 19 August 2026.
Which products and versions are affected?
Wazuh. The advisory does not name versions.
Is there a fix for CVE-2026-44253?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-44253?
Check whether you run Wazuh. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.