Skip to main content
VulnerabilityPublished Updated

CVE-2026-44253: wazuh · Excessive Memory Allocation

Affects wazuhSource GCVE Database

0

Not known to be exploited · CVSS 4.9 Medium : upgrade to 5.0.0-beta2 or 4.14.5 when convenient.

Data as of 27 Oct 2026, 12:14 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.0.0-beta2, 4.14.5
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade wazuh/wazuh to 5.0.0-beta2 or 4.14.5.

Affected software

ProductAffectedFixed in
GitHubwazuh/wazuhpkg:github/wazuh/wazuhOther threatsAffected
  • >=3.9.0 <4.14.5
  • >=5.0.0-beta1 <5.0.0-beta2
Fixed in
  • 4.14.5
  • 5.0.0-beta2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Wazuh versions 4.14.5 and 5.0.0-beta2. Users should upgrade to these or later versions to remediate the issue. No other mitigation or workaround is indicated.

Description

CVE-2026-44253 is a medium severity vulnerability in Wazuh versions from 3.9.0 up to but not including 4.14.5 and from 5.0.0-beta1 up to but not including 5.0.0-beta2. It allows an authenticated cluster node to cause memory exhaustion on the master node by sending specially crafted requests that allocate excessive memory without limits. This can disrupt agent connectivity and alert processing. The issue is fixed in Wazuh versions 4.14.5 and 5.0.0-beta2.

References

Community reviews

Loading reviews…