Quick answers
- Is CVE-2026-88922 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88922 being exploited in the wild.
- How severe is CVE-2026-88922?
- Medium severity, with a CVSS score of 6.7, published 15 September 2026.
- Which products and versions are affected?
- HashiCorp Go-Getter up to 1.8.8 and 2.2.3.
- Is there a fix for CVE-2026-88922?
- A patch was published on 2026-09-15: Fixed in go-getter 1.8.9 and 2.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88922 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-88922?
- Check whether you run HashiCorp Go-Getter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in go-getter's archive decompression handling, which applies permission metadata from archive entries without restricting them to standard read, write, and execute permissions. This allows an attacker to craft a malicious archive containing entries with elevated permission bits (such as setuid/setgid bits). When extracted by a privileged user, a local actor with access to the destination directory can exploit these elevated permissions to obtain the privileges of the extracting process. The attack requires the extraction of untrusted or attacker-controlled archives and local filesystem access to the extraction destination. The fix, available in go-getter 1.8.9 and 2.2.4, restricts extracted files to only standard permissions.
Affected products
- HashiCorp go-getter up to 1.8.8 and 2.2.3
Timeline
- 2026-09-15: disclosed
- 2026-09-15: patched: Fixed in go-getter 1.8.9 and 2.2.4