# CVE-2026-112334: Wazuh Agent out-of-bounds write in wazuh-execd

Source: https://junglewise.ai/threats/cve-2026-112334-wazuh-from-1-0-0-before-4-14-9-contains-an-out-of-bounds-write  
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-112334 · Severity: medium · CVSS 4.9 · Published 2026-11-06

Wazuh is a security monitoring and incident response platform installed on servers and endpoints. A flaw in its Active Response engine (wazuh-execd) allows privileged attackers who control the manager's configuration to corrupt memory on agent systems by defining more than 64 response commands. This leads to crashes that disable Active Response across the entire fleet and could potentially enable 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-112334 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112334 being exploited in the wild.

**How severe is CVE-2026-112334?** Medium severity, with a CVSS score of 4.9, 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-112334?** 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-112334 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-112334?** 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

An out-of-bounds write vulnerability exists in wazuh-execd's ReadExecConfig() function, which loads Active Response commands into fixed-size static arrays dimensioned for MAX_AR (64). The code lacks bounds checking and writes past the array limits into adjacent global data structures. The attack vector is the manager's ossec.conf file, which is parsed and merged into shared ar.conf files distributed to all agents; an attacker with manager configuration privileges can supply over 64 commands to trigger the overflow on every agent.

## Affected products

- Wazuh Wazuh Agent 1.0.0 before 4.14.9

## Timeline

- 2026-11-06: disclosed

## 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-f4pj-j296-jwp2](https://github.com/wazuh/wazuh/security/advisories/GHSA-f4pj-j296-jwp2)

## 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 stack-based buffer overflow in snort-full log reader](https://junglewise.ai/threats/cve-2026-112335-wazuh-agent-from-1-0-0-before-4-14-9-contains-a-stack-based)
- [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)