Loading vulnerability…
CVE-2026-22184 is a global buffer overflow in zlib versions up to and including 1.3.1.2, specifically in the standalone untgz utility under contrib/untgz, not in the core zlib compression library. The flaw is reported in TGZfname(), where an attacker-controlled archive name supplied via the command line is copied with an unbounded strcpy() into a fixed-size 1024-byte static/global buffer. If the provided archive name exceeds the buffer size, the copy causes an out-of-bounds write before archive parsing or validation, resulting in memory corruption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability in zlib addressed in Alpine Linux stable releases 3.20.10, 3.21.7, 3.22.4, and 3.23.4.
A critical buffer overflow vulnerability in zlib described as a 'global buffer overflow' with a CVSS score of 9.3.
A critical buffer overflow vulnerability in zlib's untgz utility, allowing out-of-bounds write, memory corruption, denial of service, and potentially code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.