CVE-2026-22184: zlib <= 1.3.1.2 untgz Global Buffer Overflow in TGZfname()
zlib versions up to and including 1.3.1.2 include a global buffer overflow in the untgz utility located under contrib/untgz. The vulnerability is limited to the standalone demonstration utility and does not affect the core zlib compression library. The flaw occurs when a user executes the untgz command with an excessively long archive name supplied via the command line, leading to an out-of-bounds write in a fixed-size global buffer.
Security readout for executives and security teams
Plain-English summary
CVE-2026-22184 is a buffer overflow in zlib’s standalone contrib/untgz demonstration utility, not the core zlib compression library. Business risk depends on whether that demo command is shipped or used in your environment. The source bundle does not show active exploitation or a named vendor patch.
Executive priority
Treat this as high priority for environments that ship or automate the untgz utility, but not as a broad zlib-library emergency. The immediate business task is exposure confirmation, because the core compression library is described as unaffected.
Technical view
The flaw is an out-of-bounds write in TGZfname(), triggered by an excessively long archive name passed to the untgz command line. Sources classify it as CWE-120 and CWE-787 with CVSS 3.1 score 8.6. Evidence says normal zlib library use is unaffected; exposure is limited to the standalone untgz utility.
Likely exposure
Exposure is likely narrow: systems packaging, distributing, or invoking contrib/untgz from zlib up to and including 1.3.1.2. Applications merely linking against core zlib compression functions are described as unaffected in the source bundle.
Exploitation context
Public technical details and an exploit-tagged Full Disclosure reference exist, but the bundle marks KEV false and provides no cited evidence of active exploitation. The CVSS vector and command-line trigger description appear somewhat inconsistent, so validate against vendor and distro advisories.
Researcher notes
Key uncertainty is scope. The bundle says zlib up to 1.3.1.2 includes vulnerable contrib/untgz, while affected metadata shows defaultStatus unaffected. Avoid extrapolating to all zlib consumers; focus validation on the standalone demo utility and downstream packaging decisions.
Mitigation direction
Inventory whether contrib/untgz is built, shipped, or callable in your environment.
Check zlib and operating-system vendor guidance for an official fix or package status.
Remove or disable the standalone untgz utility where it is not required.
Restrict who can execute untgz until vendor guidance is confirmed.
Prioritize remediation for systems where untgz handles untrusted filenames or archives.
Validation and detection
Search packages, build artifacts, and containers for the standalone untgz binary.
Confirm whether applications use core zlib only or invoke contrib/untgz directly.
Review distribution advisories, especially Red Hat status pages, for affected package decisions.
Check logs and job definitions for untgz execution on untrusted archive names.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.