Memory exhaustion via unbounded zlib decompression
Published Aug 18, 2026 · Updated Aug 18, 2026
Denial of service in cluster archive handling in Wazuh manager before 4.14.7 allows remote authenticated users to exhaust memory via sync archives. In framework/wazuh/core/cluster/cluster.py, decompress_files calls zlib.decompress on each peer-supplied archive member and materializes the full output in one Python bytes object without any decompressed-size limit. Exploitation requires a cluster peer with the Fernet key and reachability to the master cluster port, and the observed consequence is memory exhaustion that can OOM-kill wazuh-clusterd rather than data theft or code execution.
Summary
What happened
Denial of service in cluster archive handling in Wazuh manager before 4.14.7 allows remote authenticated users to exhaust memory via sync archives. In framework/wazuh/core/cluster/cluster.py, decompress_files calls zlib.decompress on each peer-supplied archive member and materializes the full output in one Python bytes object without any decompressed-size limit. Exploitation requires a cluster peer with the Fernet key and reachability to the master cluster port, and the observed consequence is memory exhaustion that can OOM-kill wazuh-clusterd rather than data theft or code execution.
The record
- CVE
- CVE-2026-74046
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Wazuh
- Product
- Wazuh manager
- Classifications
- CWE-409, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.14.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub Security Advisory proof of concept for GHSA-mr7j-w2m4-vw5jproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo