HashiCorp go-getter Archive Decompression privileges management

Summaryinfo

A vulnerability has been found in HashiCorp go-getter and classified as problematic. Impacted is an unknown function of the component Archive Decompression Handler. Performing a manipulation results in privileges management. This vulnerability was named CVE-2026-88922. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in HashiCorp go-getter (the affected version unknown). It has been classified as problematic. This affects an unknown part of the component Archive Decompression Handler. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at discuss.hashicorp.com. This vulnerability is uniquely identified as CVE-2026-88922 since 09/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/15/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-79245). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• HashiCorp

Name

• go-getter

License

• open-source

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion