Go-getter vulnerable to a path traversal in S3/GCS directory download handling
Summary
| CVE | CVE-2026-19585 |
|---|---|
| State | PUBLISHED |
| Assigner | HashiCorp |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-08 16:17:10 UTC |
| Updated | 2026-10-08 21:07:57 UTC |
| Description | HashiCorp go-getter versions before 1.8.10 and go-getter/v2 versions before 2.2.5 are vulnerable to path traversal during S3 and GCS directory downloads, which may allow files to be written outside the requested destination. This vulnerability (CVE-2026-19585) is fixed in go-getter 1.8.10 and go-getter/v2 2.2.5. |
Risk And Classification
Primary CVSS: v3.1 5.3 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS: 0.002080000 probability, percentile 0.099990000 (date 2026-10-10)
Problem Types: CWE-22 | CWE-22 CWE-22: Improper Limitation of a Pathname to a Restricted Directory (Path Traversal)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 5.3 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N |
| 3.1 | CNA | CVSS | 5.3 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
NoneUser Interaction
RequiredScope
UnchangedConfidentiality
NoneIntegrity
HighAvailability
NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | HashiCorp | Shared Library | affected 1.0.1 2.2.5 semver | 64 bit, 32 bit, x86, ARM, MacOS, Windows, Linux |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| discuss.hashicorp.com/t/hcsec-2026-44-go-getter-vulnerable-to-a-path-traversal-in-s... | [email protected] | discuss.hashicorp.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: This issue was reported to HashiCorp by Kris Kennaway. (en)
There are currently no legacy QID mappings associated with this CVE.