CVE-2026-41991

MEDIUMNVD 4.74.7
EchelonGraph scoreHIGH 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
Trending — 5 sources updated this week
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 0

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.7(high)
EPSS
1.3%
KEV
Not listed

Published

June 29, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

Gzip - GNU Project - Free Software Foundation

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugzip (1.14-1~exp2ubuntu1.1) @ resolute2026-07-06ubuntu
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.

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 20× in last 7d / 22× 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.

  1. 2026-07-06 23:54 UTCEG score recompute
  2. 2026-07-06 23:54 UTCVendor advisory
  3. 2026-07-06 23:53 UTCGHSA enrichment
  4. 2026-07-05 21:57 UTCEG score recompute
  5. 2026-07-05 21:57 UTCVendor advisory
  6. 2026-07-05 21:57 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 20:05 UTCEG score recompute
  9. 2026-07-04 20:05 UTCVendor advisory
  10. 2026-07-04 20:05 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 18:14 UTCEG score recompute
  13. 2026-07-03 18:14 UTCVendor advisory
  14. 2026-07-03 18:14 UTCGHSA enrichment
  15. 2026-07-02 16:21 UTCEG score recompute 2.70
  16. 2026-07-02 16:21 UTCVendor advisory
  17. 2026-07-02 16:21 UTCGHSA enrichment
  18. 2026-07-02 01:21 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-29 12:03 UTCEG score recompute
  22. 2026-06-29 12:02 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database 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 1.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41991, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.