NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

HashiCorp go-getter unsafe downloads could lead to arbitrary host accessGHSA-cjr4-fv6c-f3mv

HIGHFix: hashicorp/go-getter#359

GHSA-cjr4-fv6c-f3mv is a high-severity (CVSS 8.6) remote code execution vulnerability in github.com/hashicorp/go-getter. A fix is available for github.com/hashicorp/go-getter — see the affected versions and patch details below.

Also known asCVE-2022-26945CVE-2022-30321CVE-2022-30322CVE-2022-30323GHSA-28r2-q6m8-9hpxGHSA-fcgg-rvwg-jv58
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.00%0.75%1.50%2.24%0.1%1.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
🐹github.com/hashicorp/go-getter🐹github.com/hashicorp/go-getter🐹github.com/hashicorp/go-getter/v2🐹github.com/hashicorp/go-getter/s3/v2🐹github.com/hashicorp/go-getter/gcs/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

HashiCorp go-getter through 2.0.2 does not safely perform downloads. Arbitrary host access was possible via go-getter path traversal, symlink processing, and command injection flaws.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/go-getterall versions1.6.1go get github.com/hashicorp/go-getter@v1.6.1
🐹Gogithub.com/hashicorp/go-getter≥ 2.0.0&&< 2.1.02.1.0go get github.com/hashicorp/go-getter@v2.1.0
🐹Gogithub.com/hashicorp/go-getter/v2all versions2.1.0go get github.com/hashicorp/go-getter/v2@v2.1.0
🐹Gogithub.com/hashicorp/go-getter/s3/v2all versions2.1.0go get github.com/hashicorp/go-getter/s3/v2@v2.1.0
🐹Gogithub.com/hashicorp/go-getter/gcs/v2all versions2.1.0go get github.com/hashicorp/go-getter/gcs/v2@v2.1.0

Affected Products

1 product · 2 configurations
Application
go-getterhashicorp
≤ 1.5.11
1 version
2.0.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/go-getter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/hashicorp/go-getter to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjr4-fv6c-f3mv is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
Workaround published by Red Hat
The fix includes new configuration options to help limit the security exposure and have more secure defaults.
Source: Red Hat security advisory for GHSA-cjr4-fv6c-f3mv (CC BY 4.0)
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 4.10openshift4/ose-baremetal-rhel8-operator:v4.10.0-202208182025.p0.g97ce15e.assembly.streamRHSA-2022:6133
Red Hat OpenShift Container Platform 4.10openshift4/ose-cluster-baremetal-operator-rhel8:v4.10.0-202208260945.p0.g23614bb.assembly.streamRHSA-2022:6258
Red Hat OpenShift Container Platform 4.10openshift4/ose-baremetal-machine-controllers:v4.10.0-202209301647.p0.gadff401.assembly.streamRHSA-2022:6805
Red Hat OpenShift Container Platform 4.10openshift4/ose-installer:v4.10.0-202210250219.p0.g1ffe666.assembly.streamRHSA-2022:7211
Red Hat OpenShift Container Platform 4.11openshift4/ose-baremetal-machine-controllers:v4.11.0-202208020235.p0.ga65be86.assembly.streamRHSA-2022:5069
Red Hat OpenShift Container Platform 4.11openshift4/ose-installer:v4.11.0-202210250857.p0.g9d1e216.assembly.streamRHSA-2022:7201
Red Hat OpenShift Container Platform 4.8openshift4/ose-baremetal-rhel8-operator:v4.8.0-202208241844.p0.g5492cf5.assembly.streamRHSA-2022:6308
Red Hat OpenShift Container Platform 4.8openshift4/ose-cluster-baremetal-operator-rhel8:v4.8.0-202209291426.p0.g117d47a.assembly.streamRHSA-2022:6801

Frequently Asked Questions

HashiCorp go-getter through 2.0.2 does not safely perform downloads. Arbitrary host access was possible via go-getter path traversal, symlink processing, and command injection flaws.
O3 Security · Impact-Aware SCA

Is GHSA-cjr4-fv6c-f3mv in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
HashiCorp go-getter unsafe downloads could lead to…