CVE-2022-26945 — go-getter
HIGHCVE-2022-26945 is a high-severity (CVSS 8.6) 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.
HashiCorp go-getter unsafe downloads could lead to asymmetric resource exhaustion
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-26945 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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/v2Real-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
go-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. Fixed in 1.6.1 and 2.1.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hashicorp/go-getter | all versions | 1.6.1go get github.com/hashicorp/go-getter@v1.6.1 |
| 🐹Go | github.com/hashicorp/go-getter | ≥ 2.0.0&&< 2.1.0 | 2.1.0go get github.com/hashicorp/go-getter@v2.1.0 |
| 🐹Go | github.com/hashicorp/go-getter/v2 | all versions | 2.1.0go get github.com/hashicorp/go-getter/v2@v2.1.0 |
| 🐹Go | github.com/hashicorp/go-getter/s3/v2 | all versions | 2.1.0go get github.com/hashicorp/go-getter/s3/v2@v2.1.0 |
| 🐹Go | github.com/hashicorp/go-getter/gcs/v2 | all versions | 2.1.0go get github.com/hashicorp/go-getter/gcs/v2@v2.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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 CVE-2022-26945 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-26945 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-26945. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.10 | openshift4/ose-baremetal-rhel8-operator:v4.10.0-202208182025.p0.g97ce15e.assembly.stream | RHSA-2022:6133 |
| Red Hat OpenShift Container Platform 4.10 | openshift4/ose-cluster-baremetal-operator-rhel8:v4.10.0-202208260945.p0.g23614bb.assembly.stream | RHSA-2022:6258 |
| Red Hat OpenShift Container Platform 4.10 | openshift4/ose-baremetal-machine-controllers:v4.10.0-202209301647.p0.gadff401.assembly.stream | RHSA-2022:6805 |
| Red Hat OpenShift Container Platform 4.10 | openshift4/ose-installer:v4.10.0-202210250219.p0.g1ffe666.assembly.stream | RHSA-2022:7211 |
| Red Hat OpenShift Container Platform 4.11 | openshift4/ose-baremetal-machine-controllers:v4.11.0-202208020235.p0.ga65be86.assembly.stream | RHSA-2022:5069 |
| Red Hat OpenShift Container Platform 4.11 | openshift4/ose-installer:v4.11.0-202210250857.p0.g9d1e216.assembly.stream | RHSA-2022:7201 |
| Red Hat OpenShift Container Platform 4.8 | openshift4/ose-baremetal-rhel8-operator:v4.8.0-202208241844.p0.g5492cf5.assembly.stream | RHSA-2022:6308 |
| Red Hat OpenShift Container Platform 4.8 | openshift4/ose-cluster-baremetal-operator-rhel8:v4.8.0-202209291426.p0.g117d47a.assembly.stream | RHSA-2022:6801 |
Frequently Asked Questions
Is CVE-2022-26945 in your dependencies?
O3 Security finds CVE-2022-26945 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.