Quick answers
- Is CVE-2026-74045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74045 being exploited in the wild.
- How severe is CVE-2026-74045?
- High severity, with a CVSS score of 7.1, published 13 October 2026.
- Which products and versions are affected?
- Wazuh Manager 3.12.0 to 4.14.7.
- Is there a fix for CVE-2026-74045?
- Yes: fixed in 4.14.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74045 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-74045?
- Check whether you run Wazuh Manager 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.8
Technical details
A heap buffer overflow in wazuh-analysisd's fim_generate_alert() function occurs because full_log is allocated based on input length but written using snprintf with OS_MAXSTR (65535) as the size limit, causing writes past the allocation when generated alert text exceeds the smaller allocation. An enrolled agent can send a crafted FIM syscheck event with inflated JSON values (such as 9e18 exponents) that expand during text generation, reliably corrupting heap metadata and terminating the analysis daemon.
Affected products
- Wazuh wazuh-manager 3.12.0 to 4.14.7
Timeline
- 2026-10-13: disclosed