# CVE-2026-74030: Wazuh 3.9.0 before 4.14.8 Memory Exhaustion via SCA YAML Alias Expansion

> Attackers controlling the Wazuh manager can exhaust agent memory via malicious YAML policies, causing denial of service on agents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-x8v7-g49q-ff7j

## What is CVE-2026-74030?

CVE-2026-74030 is a medium-severity denial of service vulnerability in wazuh-agent, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Wazuh from 3.9.0 before 4.14.8 contains an uncontrolled YAML alias expansion vulnerability in yaml2json_node that allows a manager-controlled policy to exhaust agent memory. Attackers controlling the manager can push a small SCA policy with nested aliases via merged.mg to OOM-kill wazuh-modulesd on every agent in a group.

Weakness: CWE-776 (Improper Restriction of Recursive Entity References in DTDs)

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


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

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

## Is CVE-2026-74030 being exploited?

There is no known exploitation of CVE-2026-74030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74030 is a medium-severity denial of service vulnerability in wazuh-agent, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74030 in the wild and no public exploit code.

Affected product: wazuh-agent. 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-74030/ (Markdown: https://insights.sbomify.com/CVE-2026-74030/index.md)
```

## Sources

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

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