CVE-2026-41991

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory (severity: LOW) published 2026-06-29. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user’s PATH, gzexe falls back to constructing a temporary file path based solely on the process ID (PID). This predictable filename is created without exclusive access or existence checks. A local attacker can pre‑create the predicted temporary file path as a symbolic link pointing to an arbitrary file writable by the victim. When gzexe runs, it follows the symlink and overwrites the target file, resulting in a time‑of‑check to time‑of‑use (TOCTOU) condition that allows arbitrary file overwrite.

This issue has been fixed in the commit 4e6f8b24ab823146ab8776f0b7fe486ab34d4269

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

Published

June 29, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available.
generic

Gzip - GNU Project - Free Software Foundation

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

gzexe: use -C if lacking mktemp - gzip.git - gzip

https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=4e6f8b24ab823146ab8776f0b7fe486ab34d4269

Vendor Advisories for CVE-2026-41991(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

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

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41991?
CVE-2026-41991 is a medium vulnerability published on June 29, 2026. GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user’s PATH, gzexe falls back to constructing a temporary file path based solely on the process ID (PID). This predictable filename is created without…
When was CVE-2026-41991 disclosed?
CVE-2026-41991 was first published on June 29, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41991 actively exploited?
CVE-2026-41991 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41991?
CVE-2026-41991 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-41991?
A fix for CVE-2026-41991 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41991 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-41991

Explore →

Is Your Infrastructure Affected by CVE-2026-41991?

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

Book a Demo →Browse All CVEs