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

> An enrolled agent can crash the Wazuh manager via a heap buffer overflow in the FIM decoder, causing a fleet-wide detection outage.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-gc4j-j9fg-4cfr

## What is CVE-2026-74045?

CVE-2026-74045 is a high-severity memory corruption vulnerability in wazuh-manager, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-74045?


## How do I fix CVE-2026-74045?

No fix has been published for CVE-2026-74045 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-74045 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74045 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74045 and fix it if it is affected.

What it is: CVE-2026-74045 is a high-severity memory corruption vulnerability in wazuh-manager, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74045 exists.

Affected product: wazuh-manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74045/ (Markdown: https://insights.sbomify.com/CVE-2026-74045/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74045
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74045
- OSV: https://osv.dev/vulnerability/CVE-2026-74045

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74045/
Summaries are generated and may contain mistakes; the official description above is the record.