Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-41992: GNU gzip LZH Out-of-Bounds Read Through Stale Shared Decompression State

Published Jun 29, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days7 mentions · peak 2 in a dayToday
CVSS6.9Medium · v4
EPSS0.62%50th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
GNU Project
IdentifiersCVE-2026-41992CWE-125

GNU gzip contains an out-of-bounds read vulnerability in its LZH decompression logic caused by improper reuse of global state across decompression formats. A global array shared by the LZ77, LZW, and LZH routines is not reinitialized between files processed in the same invocation. Processing a specially crafted LZW file first poisons this shared state; subsequent processing of a specially crafted LZH file causes the decoder to follow stale array values and read beyond the allocated global buffer. Exploitation may disclose adjacent process memory or crash gzip.

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.

Successful exploitation may expose sensitive information from memory adjacent to the shared global buffer. Invalid memory accesses may also crash gzip, causing denial of service in the decompression operation and potentially disrupting dependent workflows. Arbitrary code execution, memory writes, and integrity compromise are not established.

Mitigation

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

Until patched, avoid processing untrusted LZW and LZH inputs together in one gzip invocation. Process each untrusted file in a separate execution to prevent shared state from carrying over between files. Where feasible, reject untrusted legacy compressed formats or suspend their decompression.

Remediation

Patch, then assume compromise.

Update GNU gzip using the applicable vendor security package or a release incorporating upstream fixes 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d. Identified fixed packages include gzip 1.12-5.ph5 for Photon OS 5.0 and gzip 1.6-4ubuntu1+esm2 for Ubuntu 16.04 LTS, with the latter available through Ubuntu Pro with Legacy Support. For affected ExtremeAnalytics for Site Engine, ExtremeCloud IQ - Site Engine, and ExtremeControl for Site Engine deployments, upgrade to version 26.8.10 or later. Exact affected upstream version ranges and the first fixed upstream release are not specified.

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
GNU ProjectGzipapplication
FAQ

Frequently asked questions

Is CVE-2026-41992 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-41992 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41992?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-41992, the earliest disclosed Oct 13, 2026.
Is there a patch for CVE-2026-41992?
Update GNU gzip using the applicable vendor security package or a release incorporating upstream fixes 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d. Identified fixed packages include gzip 1.12-5.ph5 for Photon OS 5.0 and gzip 1.6-4ubuntu1+esm2 for Ubuntu 16.04 LTS, with the latter available through Ubuntu Pro with Legacy Support.
What products are affected by CVE-2026-41992?
GNU Project Gzip.
How severe is CVE-2026-41992?
CVE-2026-41992 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.62% (50th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.10.1 : gzip (EulerOS-SA-2026-4989) | Tenable®A vulnerability affecting gzip in EulerOS Virtualization 2.10.1, addressed by advisory EulerOS-SA-2026-4989. The entry reports available exploits and a patch publication date of November 17, 2026, but provides no technical description of the flaw.Read more ↗tenable nessus pluginsNews · Nov 16, 2026EulerOS Virtualization 2.10.0 : gzip (EulerOS-SA-2026-5030) | Tenable®A vulnerability affecting gzip in EulerOS Virtualization 2.10.0. The listed CVSS vectors indicate high confidentiality impact without integrity or availability impact, but disagree on whether the attack vector is network or local. Exploits and a patch are available; the content does not describe the underlying flaw.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 9.6 [CIQ] Security Update: gzip Multiple Vulnerabi... | Tenable®A vulnerability affecting the gzip package on Rocky Linux 9.6, addressed by CIQ advisory ciqsa-2026_1813. The supplied CVSS vectors indicate high confidentiality impact without integrity or availability impact. The temporal exploit maturity value E:P indicates proof-of-concept exploit availability. The content does not explain the underlying flaw.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : gzip (EulerOS-SA-2026-4759) | Tenable®A shared-global-state vulnerability in GNU gzip's LZH decompression logic causes out-of-bounds reads from a global buffer. Processing a crafted LZW file followed by a crafted LZH file in the same invocation leaves stale array values that the LZH decoder subsequently follows. The advisory identifies fix commit 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and recommends updating affected gzip packages. Nessus detects affected versions rather than testing exploitation. Exploit availability is reported at the combined advisory level, without identifying which individual vulnerability it applies to.Read more ↗
+40 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 activity36Community discussion across Reddit, Mastodon, and other social sources.