# CVE-2026-112335: Wazuh agent stack-based buffer overflow in snort-full log reader

Source: https://junglewise.ai/threats/cve-2026-112335-wazuh-agent-from-1-0-0-before-4-14-9-contains-a-stack-based  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-112335 · Severity: medium · CVSS 5.5 · Published 2026-11-06

Wazuh agent is security monitoring software that collects and analyzes logs from endpoints and servers. The agent contains a buffer overflow vulnerability in its snort-full log parser that allows attackers to crash the agent or execute code with SYSTEM privileges on Windows by crafting malicious log entries. On 32-bit Windows agents running as SYSTEM, attackers can overwrite an exception handler to achieve code execution.

Technologies: [Wazuh Agent](https://junglewise.ai/threats/technologies/wazuh-agent). Vendors: [Wazuh](https://junglewise.ai/threats/vendors/wazuh).

## Quick answers

**Is CVE-2026-112335 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112335 being exploited in the wild.

**How severe is CVE-2026-112335?** Medium severity, with a CVSS score of 5.5, published 6 November 2026.

**Which products and versions are affected?** Wazuh Agent 1.0.0 before 4.14.9.

**Is there a fix for CVE-2026-112335?** Yes: fixed in 4.14.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-112335 attacked?** It is attacked with local access, in a hosted service.

**Am I affected by CVE-2026-112335?** Check whether you run Wazuh Agent at an affected version. 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.

## How to fix

- Fixed in 4.14.9

## Technical details

A stack-based buffer overflow exists in read_snortfull() due to incorrect buffer accounting: the function decrements the remaining space counter by the full line length even though strncat() may append fewer bytes, causing an integer underflow. Once the counter becomes negative, it is converted to a huge size_t value on the next strncat() call, resulting in an unbounded copy of attacker-controlled data past the 65,280-byte stack buffer. The vulnerability is reachable only on Windows agents through the snort-full log format; Linux agents are accidentally protected by a separate dispatcher bug that routes snort-full logs to the wrong parser.

## Affected products

- Wazuh agent 1.0.0 before 4.14.9

## Timeline

- 2026-11-06: disclosed
- 2026-10-15: patched

## References

- [https://github.com/wazuh/wazuh/releases/tag/v4.14.9](https://github.com/wazuh/wazuh/releases/tag/v4.14.9)
- [https://github.com/wazuh/wazuh/security/advisories/GHSA-3gq8-gg8f-5h8h](https://github.com/wazuh/wazuh/security/advisories/GHSA-3gq8-gg8f-5h8h)

## Related threats

- [Wazuh missing TLS hostname verification in fluent-forward module](https://junglewise.ai/threats/cve-2026-112339-wazuh-from-3-9-0-before-4-14-9-contains-a-missing-tls-hostname)
- [Wazuh GitHub module server-side request forgery in pagination](https://junglewise.ai/threats/cve-2026-112338-wazuh-from-4-3-0-before-4-14-9-contains-a-server-side-request)
- [Wazuh Agent out-of-bounds write in wazuh-execd](https://junglewise.ai/threats/cve-2026-112334-wazuh-from-1-0-0-before-4-14-9-contains-an-out-of-bounds-write)
- [Wazuh remote code execution via SCA policy path validation](https://junglewise.ai/threats/cve-2026-74036-wazuh-from-4-3-0-before-4-14-8-contains-a-remote-code-execution)
- [Wazuh YAML alias expansion memory exhaustion in SCA](https://junglewise.ai/threats/cve-2026-74030-wazuh-from-3-9-0-before-4-14-8-contains-an-uncontrolled-yaml)
