CVE-2026-41992

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory published 2026-06-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression routines and is not reinitialized between files processed in the same invocation. By decompressing a specially crafted LZW file followed by a specially crafted LZH file in a single gzip -d command, an attacker can poison the shared global state and subsequently trigger an out‑of‑bounds read in the LZH decoder. The LZH decompression logic follows stale values left in the shared array, causing reads past the end of the allocated global buffer.

This issue has been fixed in commits 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

June 29, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Patch available.
generic

Gzip - GNU Project - Free Software Foundation

https://www.gnu.org/software/gzip/

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugzip (1.6-4ubuntu1+esm2) @ xenial2026-09-23ubuntu
ubuntugzip (1.14-1~exp2ubuntu1.1) @ resolute2026-09-23ubuntu
redhatrhui5/rhua-rhel9:17888805812026-09-09redhat
redhatgzip-0:1.9-15.el8_102026-09-09redhat
redhatgzip-0:1.12-2.el9_82026-08-31redhat
redhatdiscovery/discovery-server-rhel9:17882057792026-08-31redhat
redhatgzip-0:1.13-4.el10_22026-08-31redhat
redhatgzip-main-1.14-2.3.hum12026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
gzip—
  • every version up to 1.13-r1: fixed in 1.13-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
gzip—
  • every version up to 1.14-r2: fixed in 1.14-r2
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
gzip—
  • every version up to 1.14-r3: fixed in 1.14-r3
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
gzip—
  • every version up to 1.14-r3: fixed in 1.14-r3
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gzip1.10-4 ... 1.14-1~exp2 (9 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gzip1.12-1 ... 1.14-1~exp2 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gzip1.13-1
  • every version up to 1.13-1+deb13u1: fixed in 1.13-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gzip1.13-1, 1.13.56~e549-1~exp1, 1.14-1~exp1, 1.14-1~exp2
  • every version up to 1.14-1: fixed in 1.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 344 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-23 17:53 UTCEPSS rescore
  13. 2026-09-23 07:34 UTCEG score recompute
  14. 2026-09-23 07:34 UTCVendor advisory
  15. 2026-09-23 07:34 UTCGHSA enrichment
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 07:00 UTCEG score recompute
  19. 2026-09-18 07:00 UTCVendor advisory
  20. 2026-09-18 07:00 UTCGHSA enrichment
  21. 2026-09-17 19:31 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-14 00:53 UTCEG score recompute
  25. 2026-09-14 00:53 UTCVendor advisory
Show 75 more
  1. 2026-09-14 00:53 UTCGHSA enrichment
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-13 09:26 UTCVendor advisory
  4. 2026-09-13 09:26 UTCGHSA enrichment
  5. 2026-09-12 15:16 UTCEG score recompute
  6. 2026-09-12 15:16 UTCVendor advisory
  7. 2026-09-12 15:16 UTCGHSA enrichment
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 14:45 UTCEG score recompute
  15. 2026-09-06 14:45 UTCVendor advisory
  16. 2026-09-06 14:45 UTCGHSA enrichment
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-04 05:06 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:53 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 18:49 UTCEG score recompute
  24. 2026-08-30 18:49 UTCVendor advisory
  25. 2026-08-30 18:49 UTCGHSA enrichment
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-28 21:41 UTCEPSS rescore
  28. 2026-08-28 02:53 UTCEG score recompute
  29. 2026-08-28 02:53 UTCVendor advisory
  30. 2026-08-28 02:53 UTCGHSA enrichment
  31. 2026-08-27 14:25 UTCEPSS rescore
  32. 2026-08-27 13:34 UTCVendor advisory
  33. 2026-08-27 13:34 UTCGHSA enrichment
  34. 2026-08-27 13:01 UTCVendor advisory
  35. 2026-08-27 13:01 UTCGHSA enrichment
  36. 2026-08-27 06:40 UTCEG score recompute
  37. 2026-08-27 06:40 UTCVendor advisory
  38. 2026-08-27 06:40 UTCGHSA enrichment
  39. 2026-08-26 14:46 UTCEPSS rescore
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-25 04:24 UTCVendor advisory
  42. 2026-08-25 04:24 UTCGHSA enrichment
  43. 2026-08-25 03:30 UTCVendor advisory
  44. 2026-08-25 03:30 UTCGHSA enrichment
  45. 2026-08-24 23:56 UTCEG score recompute
  46. 2026-08-24 23:56 UTCVendor advisory
  47. 2026-08-24 23:56 UTCGHSA enrichment
  48. 2026-08-24 12:41 UTCEG score recompute
  49. 2026-08-24 12:41 UTCVendor advisory
  50. 2026-08-24 12:41 UTCGHSA enrichment
  51. 2026-08-23 20:25 UTCVendor advisory
  52. 2026-08-23 20:25 UTCGHSA enrichment
  53. 2026-08-23 19:16 UTCVendor advisory
  54. 2026-08-23 19:16 UTCGHSA enrichment
  55. 2026-08-23 08:30 UTCEG score recompute
  56. 2026-08-23 08:30 UTCVendor advisory
  57. 2026-08-23 08:30 UTCGHSA enrichment
  58. 2026-08-23 00:19 UTCEPSS rescore
  59. 2026-08-22 20:56 UTCVendor advisory
  60. 2026-08-22 20:56 UTCGHSA enrichment
  61. 2026-08-22 09:06 UTCEG score recompute
  62. 2026-08-22 09:06 UTCVendor advisory
  63. 2026-08-22 09:06 UTCGHSA enrichment
  64. 2026-08-21 23:49 UTCEPSS rescore
  65. 2026-08-21 17:23 UTCVendor advisory
  66. 2026-08-21 17:23 UTCGHSA enrichment
  67. 2026-08-21 04:54 UTCEG score recompute
  68. 2026-08-21 04:54 UTCVendor advisory
  69. 2026-08-21 04:54 UTCGHSA enrichment
  70. 2026-08-20 22:55 UTCEPSS rescore
  71. 2026-08-20 17:15 UTCVendor advisory
  72. 2026-08-20 17:15 UTCGHSA enrichment
  73. 2026-08-20 05:52 UTCEG score recompute
  74. 2026-08-20 05:52 UTCVendor advisory
  75. 2026-08-20 05:52 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-41992?
CVE-2026-41992 is a high vulnerability published on June 29, 2026. GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression…
When was CVE-2026-41992 disclosed?
CVE-2026-41992 was first published on June 29, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41992 actively exploited?
CVE-2026-41992 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41992?
CVE-2026-41992 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41992?
A fix for CVE-2026-41992 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41992 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41992

Explore →

Is Your Infrastructure Affected by CVE-2026-41992?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.