# CVE-2026-74046: Wazuh 4.4.0 < 4.14.7 DoS via fdecompress_files() Zip Bomb

> Authenticated cluster peers can cause memory exhaustion and service disruption on Wazuh master nodes by uploading malicious zip bomb archives.

- **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:** 18 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-mr7j-w2m4-vw5j

## What is CVE-2026-74046?

CVE-2026-74046 is a medium-severity denial of service vulnerability in Wazuh Wazuh, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Wazuh 4.4.0 before 4.14.7 contains a denial of service vulnerability in the fdecompress_files() function within cluster.py that allows authenticated cluster peers to exhaust memory by supplying a malicious synchronization archive without decompressed size limits. Attackers holding a valid cluster Fernet key can upload a small, highly compressed zip bomb archive that forces wazuh-clusterd on the master node to decompress the full payload into memory, causing memory exhaustion and service disruption.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

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

It affects 1 product.


Products: Wazuh Wazuh.

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

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

## Is CVE-2026-74046 being exploited?

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

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74046 is a medium-severity denial of service vulnerability in Wazuh Wazuh, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74046 exists.

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

## Sources

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

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