HashiCorp go-getter Updates Block S3 and GCS Path Traversal

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

HashiCorp published HCSEC-2026-44 for HashiCorp go-getter 1.x and go-getter/v2 directory downloads from Amazon S3 or Google Cloud Storage. Inventory the exact affected scope, apply go-getter 1.8.10 or go-getter/v2 2.2.5, validate dependent operations, and preserve change evidence.

Validate go-getter Scope And Apply The Supported Fix

What to do now: Inventory HashiCorp go-getter 1.x and go-getter/v2 directory downloads from Amazon S3 or Google Cloud Storage, match versions and enabled features to the authority's scope, apply supported remediation, validate representative operations, and document exceptions.

Open the authoritative advisory

Last verified: 2026-10-08 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeHashiCorp go-getter 1.x and go-getter/v2 directory downloads from Amazon S3 or Google Cloud Storage
AdvisoryHCSEC-2026-44
CVECVE-2026-19585
Authoritative release date2026-10-08 15:16:21.404 UTC
Authority revision date2026-10-08 15:16:21.509 UTC
Affected versionsgo-getter through 1.8.9 and go-getter/v2 through 2.2.4 when applications download S3 or GCS directories; single-object downloads are not affected.
Fixed versiongo-getter 1.8.10 or go-getter/v2 2.2.5
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Object names returned during S3 or GCS directory downloads were not constrained to the requested destination, allowing a bucket-content attacker to write outside that directory subject to the downloader process permissions.

What To Validate Now

  1. Inventory. Locate HashiCorp go-getter 1.x and go-getter/v2 directory downloads from Amazon S3 or Google Cloud Storage; record versions, enabled features, exposure paths, owners, dependencies, support channels, and maintenance groups.
  2. Establish applicability. Compare every deployment with the authority's affected statement: go-getter through 1.8.9 and go-getter/v2 through 2.2.4 when applications download S3 or GCS directories; single-object downloads are not affected. Do not infer applicability from product family, CVSS, or Internet reachability alone.
  3. Remediate. Apply go-getter 1.8.10 or go-getter/v2 2.2.5 through the authority-supported channel and follow the current advisory.
  4. Validate. Confirm the resulting go-getter build or managed state, exercise representative services and recovery paths, monitor for regressions, and retain the result.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Trace direct and transitive library use, confirm whether untrusted bucket object names can reach directory-mode downloads, rebuild dependent binaries with the fixed module, and validate destination containment. Preserve pre-change state, installation output, logs, validation evidence, and rollback decisions.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.