CVE-2026-44254: Wazuh is a free and open source platform used for threat prevention, detection, and response. From 1.0.0 until 4.14.6…
CVE-2026-44254 · Severity: medium · CVSS 5.3 · Published 2026-08-19
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 1.0.0 until 4.14.6 and 5.0.0-beta2, HandleSecureMessage() in src/remoted/secure.c passes a pointer inside its stack buffer to ReadSecMSG(), and src/os_crypto/shared/msgs.c decompresses up to OS_MAXSTR bytes at that offset. For an encrypted agent message on TCP port 1514 that expands to 65,536 bytes, os_zlib_uncompress() writes a terminating null byte beyond the end of the destination buffer. The resulting stack out-of-bounds write in the root-level remoted daemon can crash message processing and disrupt agent communications. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.
No. Junglewise Threat Intelligence has no report of CVE-2026-44254 being exploited in the wild.
How severe is CVE-2026-44254?
Medium severity, with a CVSS score of 5.3, published 19 August 2026.
Which products and versions are affected?
Wazuh. The advisory does not name versions.
Is there a fix for CVE-2026-44254?
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-44254?
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.