Wazuh Manager 3.0.0 before 4.14.9 Memory Leak DoS via JSON Decoder
Wazuh Manager versions 3.0.0 through 4.14.7 using the stock generic JSON decoder are affected. The fix is in 4.14.9.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.14.9
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Wazuh Manager versions 3.0.0 through 4.14.7 (inclusive) with the stock generic JSON decoder Events must be JSON objects containing repeated occurrences of a static field such as id Attacker needs an agent identity, obtained in the advisory's example through passwordless TLS enrollment on TCP/1515
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wazuh Manager versions from 3.0.0 up to (but not including) the fixed release contain a memory leak in the generic JSON decoder that can be triggered remotely by an attacker who has enrolled an agent, which requires low privileges and no user action. By sending events with repeated static fields such as id, an attacker can exhaust memory in wazuh-analysisd until the process is killed, disabling alerting.
Read the original description
Wazuh Manager from 3.0.0 before 4.14.9 contains a memory leak vulnerability in the generic JSON decoder that allows remote attackers to exhaust wazuh-analysisd memory via repeated static fields. Attackers can enroll an agent through passwordless enrollment and send events with duplicate fields such as id, triggering an OOM kill that disables alerting.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Wazuh Manager versions 3.0.0 through 4.14.7 (inclusive) with the stock generic JSON decoder Events must be JSON objects containing repeated occurrences of a static field such as id Attacker needs an agent identity, obtained in the advisory's example through passwordless TLS enrollment on TCP/1515Upgrade to a fixed version: 4.14.9.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wazuh wazuh
From 3.0.0 · fixed in 4.14.9
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112336
Is CVE-2026-112336 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When a JSON event repeats a static field such as id, Wazuh Manager's wazuh-analysisd process can exhaust its memory and be killed. Once it stops, central event decoding, rule evaluation and alert generation are disabled.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-112336?
wazuh: from 3.0.0 before 4.14.9.Source: cve.now feed data
Am I affected, and how do I check?
Wazuh Manager versions 3.0.0 through 4.14.7, inclusive, with the stock generic JSON decoder. Compare the installed Wazuh Manager version against that range, and check whether the generic JSON decoder is in use.Source: github.com, vulncheck.com
How do I fix CVE-2026-112336?
Upgrade Wazuh Manager to 4.14.9 or later, which is the fixed version.Source: github.com, vulncheck.com