Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-22184: Global Buffer Overflow in zlib untgz

Published Jan 7, 2026 · Updated 15 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.6Medium · v4
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Zlib
IdentifiersCVE-2026-22184CWE-120 · Buffer Copy without Checking Size…

CVE-2026-22184 is a global buffer overflow in the standalone untgz demonstration utility distributed with zlib versions up to and including 1.3.1.2. The TGZfname() function uses an unbounded strcpy() to copy a command-line archive name into a fixed-size 1024-byte static global buffer. An excessively long argument causes an out-of-bounds write, potentially resulting in memory corruption, denial of service, or code execution. The core zlib compression library is not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can corrupt global memory and crash the untgz process. Arbitrary code execution may be possible depending on compiler, architecture, build flags, and memory layout; it is not established as a guaranteed outcome. Applications using only the core zlib compression library are not affected by this flaw.

Mitigation

If you can’t patch tonight, do this now.

Avoid invoking the vulnerable untgz utility with attacker-controlled archive names. Remove or disable the standalone utility where it is unnecessary, or enforce strict archive-name length limits before invocation. These measures apply to the demonstration utility rather than the core zlib library.

Remediation

Patch, then assume compromise.

Install a vendor or distribution update explicitly addressing CVE-2026-22184. Alpine Linux releases 3.20.10, 3.21.7, 3.22.4, and 3.23.4 include a fix, and a ZTE CGSL Main 7 patch was published on September 7, 2026. An exact fixed upstream zlib version is not established. Siemens CADRA V2511 does not resolve this vulnerability; the Siemens advisory lists no available CADRA fix for it.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ZlibZlibapplication
FAQ

Frequently asked questions

Is CVE-2026-22184 exploited in the wild?
As of Nov 3, 2026, Mallory has no reports of CVE-2026-22184 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-22184?
Yes. As of Nov 3, 2026, Mallory has reports of a public exploit for CVE-2026-22184.
Is there a patch for CVE-2026-22184?
Install a vendor or distribution update explicitly addressing CVE-2026-22184. Alpine Linux releases 3.20.10, 3.21.7, 3.22.4, and 3.23.4 include a fix, and a ZTE CGSL Main 7 patch was published on September 7, 2026.
What products are affected by CVE-2026-22184?
Zlib.
How severe is CVE-2026-22184?
CVE-2026-22184 has a CVSS v4 score of 4.6 (Medium) and an EPSS score of 0.41% (36th percentile) as of Nov 3, 2026.
Activity feed

Recent activity

26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity19Community discussion across Reddit, Mastodon, and other social sources.