Hashicorp Go-getter

9 CVEs affecting Hashicorp Go-getter. Latest disclosed: 2025-08-15. Critical: 2, High: 5.

Top CVEs affecting Hashicorp Go-getter
CVESeverityScorePublishedSummary
CVE-2024-3817Critical9.82024-04-17HashiCorp’s go-getter library is vulnerable to argument injection when executing Git to discover remote branches. This vulnerability does not affect the go-g…
CVE-2022-26945Critical9.82022-05-25go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and configuration bypass via abuse of custom HTTP response header processing. Fi…
CVE-2022-30323High8.62022-05-25go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files. Fixed in 1.6.1 and 2.1.0.
CVE-2022-30322High8.62022-05-25go-getter up to 1.5.11 and 2.0.2 allowed asymmetric resource exhaustion when go-getter processed malicious HTTP responses. Fixed in 1.6.1 and 2.1.0.
CVE-2022-30321High8.62022-05-25go-getter up to 1.5.11 and 2.0.2 allowed arbitrary host access via go-getter path traversal, symlink processing, and command injection flaws. Fixed in 1.6.1 an…
CVE-2024-6257High8.42024-06-25HashiCorp’s go-getter library can be coerced into executing Git update on an existing maliciously modified Git Configuration, potentially leading to arbitrary…
CVE-2025-8959High7.52025-08-15HashiCorp's go-getter library subdirectory download feature is vulnerable to symlink attacks leading to unauthorized read access beyond the designated director…
CVE-2022-29810Medium5.52022-04-27The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter.
CVE-2023-0475Medium4.22023-02-16HashiCorp go-getter up to 1.6.2 and 2.1.1 is vulnerable to decompression bombs. Fixed in 1.7.0 and 2.2.0.