How severe is CVE-2022-30323?

CVE-2022-30323 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-30323?

CVE-2022-30323 affects the following packages: github.com/hashicorp/go-getter (Go), github.com/hashicorp/go-getter (Go), github.com/hashicorp/go-getter/v2 (Go), github.com/hashicorp/go-getter/s3/v2 (Go), github.com/hashicorp/go-getter/gcs/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-30323?

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-30323 is resolved across your whole dependency graph.

How do I detect CVE-2022-30323 in my Go dependencies?

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.

How do I mitigate CVE-2022-30323 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-30323 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-30323 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-30323?

CVE-2022-30323 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-30323 published, and has it been updated?

CVE-2022-30323 was published on May 25, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-30323 — go-getter

HIGHFix: hashicorp/go-getter#359

CVE-2022-30323 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

Also known asCVE-2022-26945 CVE-2022-30321 CVE-2022-30322 GHSA-28r2-q6m8-9hpx GHSA-cjr4-fv6c-f3mv GHSA-fcgg-rvwg-jv58

Published

May 25, 2022

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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. Asymmetric resource exhaustion could occur when go-getter processed malicious HTTP responses.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/go-getter`	all versions	1.6.1`go get github.com/hashicorp/go-getter@v1.6.1`
🐹Go	`github.com/hashicorp/go-getter`	≥ 2.0.0&&< 2.1.0	2.1.0`go get github.com/hashicorp/go-getter@v2.1.0`
🐹Go	`github.com/hashicorp/go-getter/v2`	all versions	2.1.0`go get github.com/hashicorp/go-getter/v2@v2.1.0`
🐹Go	`github.com/hashicorp/go-getter/s3/v2`	all versions	2.1.0`go get github.com/hashicorp/go-getter/s3/v2@v2.1.0`
🐹Go	`github.com/hashicorp/go-getter/gcs/v2`	all versions	2.1.0`go 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

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.
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-30323 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 CVE-2022-30323 (CC BY 4.0)

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

HashiCorp go-getter through 2.0.2 does not safely perform downloads. Asymmetric resource exhaustion could occur when go-getter processed malicious HTTP responses.

O3 Security · Impact-Aware SCA

Is CVE-2022-30323 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works