The go-getter library up to versions 1.8.8 and 2.2.3 is vulnerable to a privilege escalation issue in its archive decompression handling that may allow a crafted archive to cause extracted files to be created with elevated permission bits. Where extraction is performed by a privileged user, this may allow a local actor to obtain the privileges of the extracting process. This vulnerability (CVE-2026-88922) is fixed in go-getter 1.8.9 and 2.2.4.
CVE-2026-88922
Score 6.7 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 6.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.7
- EG Score
- 6.7(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
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 computedSeverity67% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026HCSEC-2026-39 - Go-getter vulnerable to a privilege escalation issue in its archive decompression handling - Security - HashiCorp Discuss
https://discuss.hashicorp.com/t/hcsec-2026-39-go-getter-vulnerable-to-a-privilege-escalation-issue-in-its-archive-decompression-handling/77752Vendor Advisories for CVE-2026-88922(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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.
- 2026-09-18 19:48 UTCEG score recompute
- 2026-09-18 19:48 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 22:19 UTCEG score recompute
- 2026-09-17 22:19 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 21:29 UTCEG score recompute
- 2026-09-16 21:29 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-15 20:39 UTCEG score recompute
- 2026-09-15 19:48 UTCEG score recompute
- 2026-09-15 19:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-281
Frequently asked(5)
What is CVE-2026-88922?
When was CVE-2026-88922 disclosed?
Is CVE-2026-88922 actively exploited?
What is the CVSS score of CVE-2026-88922?
How do I remediate CVE-2026-88922?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-88922
Is Your Infrastructure Affected by CVE-2026-88922?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.