CVE-2026-88922 HashiCorp CVE debrief

Who should care

Defenders responsible for systems where privileged users perform archive extraction using the go-getter library should assess exposure and prioritize verification and remediation efforts.

Why it matters

CVE-2026-88922 allows for privilege escalation through archive decompression handling in the go-getter library, potentially enabling local actors to gain elevated privileges. Defenders should prioritize verification, remediation, and compensating controls.

• Potential privilege escalation for local actors
• Elevated risk of unauthorized access to sensitive areas
• Need for verification and remediation of vulnerable go-getter versions
• Importance of monitoring and restricting access to sensitive areas

Technical summary

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. This 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. The vulnerability is fixed in go-getter versions 1.8.9 and 2.2.4. Defenders should prioritize verifying and upgrading to go-getter versions 1.8.9 or 2.2.4, assessing exposure in systems where privileged users perform archive extraction, and implementing compensating controls such as monitoring and restricting access to sensitive areas.

Defensive priority

Defenders should prioritize verifying and upgrading to go-getter versions 1.8.9 or 2.2.4, assessing exposure in systems where privileged users perform archive extraction, and implementing compensating controls such as monitoring and restricting access to sensitive areas.

Recommended defensive actions

• Verify and upgrade to go-getter versions 1.8.9 or 2.2.4
• Assess exposure in systems where privileged users perform archive extraction
• Implement compensating controls such as monitoring and restricting access to sensitive areas
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its potential impact, and fixed versions. A source reference from Hashicorp discusses the issue and provides additional context. 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. This 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 elevated

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.