Wazuh Agent 1.0.0 before 4.14.9 Stack Buffer Overflow via read_snortfull
- Exploited
- No known exploitation
- Fix
- Fixed in 4.14.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.14.9.
- Published
- 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? →
- 7/100 · provisional
- 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
The Wazuh agent (versions before 4.14.9) has a stack buffer overflow in its snort-full log reader that a local attacker with low-privilege access can trigger by writing crafted multi-line content to a monitored log file. The overflow can crash the agent, and on 32-bit Windows agents running as SYSTEM it can also overwrite an SEH handler.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Wazuh agent from 1.0.0 before 4.14.9 contains a stack-based buffer overflow in the logcollector snort-full log reader that miscalculates remaining buffer space in read_snortfull(). Attackers who write crafted multi-line content to a monitored snort-full log can overflow the 65,280-byte stack buffer, crashing the agent or overwriting an SEH handler on 32-bit Windows agents running as SYSTEM.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.14.9.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wazuh wazuh
From 1.0.0 · fixed in 4.14.9
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112335
Is CVE-2026-112335 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
Which versions are affected by CVE-2026-112335?
wazuh: from 1.0.0 before 4.14.9.Source: cve.now feed data
How do I fix CVE-2026-112335?
Upgrade to a fixed version: 4.14.9.Source: cve.now feed data