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