Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisory

CVE-2026-41992 Lets Crafted gzip Streams Trigger Out-of-Bounds Memory Access

Vulnerability Disclosure · 4 sources · Updated 3mo ago · First seen Aug 23, 2026

CVE-2026-41992 Lets Crafted gzip Streams Trigger Out-of-Bounds Memory Access

CVE-2026-41992 affects gzip 1.14 and earlier, causing an out-of-bounds memory access when one gzip -d process decompresses specially crafted LZW data followed by specially crafted LZH data. The apparent state-reuse flaw is currently understood to require processing two malicious files in a single invocation and is expected to enable an out-of-bounds read and program crash. Michał Majchrowicz and Elias Hasas reported the issue and supplied fixes; Paul Eggert published the disclosure.

Organizations running affected gzip packages should apply the patch that clears the left and right arrays in huf_decode_start() or upgrade to gzip 1.15 when available. CentOS 9 security updates address CVE-2026-41992 alongside CVE-2026-41991. The advisory rates the issue as medium severity, while scanner metadata presents differing exploitability vectors; no known exploitation has been reported.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Jun 29, 2026 – Aug 25, 2026
  1. Aug 25, 20263mo ago

    Follow-up clarifies likely trigger and impact

    Solar Designer said the then-unconfirmed understanding was that exploitation requires gzip to process two files in one invocation, rather than one file or stream containing both formats. He assessed the likely consequence as an out-of-bounds read that crashes the program.

    oss-sec: Re: CVE-2026-41992 gzip 1.14 out-of-bounds memory buffer access
  2. Aug 22, 20263mo ago

    gzip out-of-bounds flaw publicly disclosed

    Paul Eggert disclosed CVE-2026-41992 affecting gzip 1.14 and earlier on oss-sec. Specially crafted LZW data followed by LZH data in one gzip -d process can trigger the flaw; users were advised to apply the patch or upgrade to gzip 1.15 when available.

    oss-sec: CVE-2026-41992 gzip 1.14 out-of-bounds memory buffer access
  3. Aug 19, 20263mo ago

    Patch for CVE-2026-41992 published

    A patch associated with CVE-2026-41992 was published. The mitigation clears the reused left and right decompression arrays in gzip's huf_decode_start() routine.

    CentOS 9 : gzip-1.12-2.el9 | Tenable®
  4. Jul 25, 20264mo ago

    Issue reported through linux-distros

    Solar Designer stated that the gzip issue had previously been brought to the linux-distros list on July 25.

    oss-sec: Re: CVE-2026-41992 gzip 1.14 out-of-bounds memory buffer access
  5. Jun 29, 20265mo ago

    CVE-2026-41992 vulnerability published

    CVE-2026-41992 was published for an out-of-bounds memory buffer access flaw in gzip.

    CentOS 9 : gzip-1.12-2.el9 | Tenable®
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.