CVE-2022-26945

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.

Published: 2022-05-25 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-26945 is rated High Risk (65/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.63%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-26945

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-19 1.52% 1.63% +0.10%
2 2026-06-15 0.20% 1.52% +1.33%
3 2026-05-19 — 0.20% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26945

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2022-26945

GitHub Security Advisory for CVE-2022-26945

GHSA-x24g-9w7v-vprh · Severity: critical · Ecosystem: go — HashiCorp go-getter command injection

OS Trackers for CVE-2022-26945

vendor priority summary link
debian not yet assigned CVE-2022-26945 not yet assigned priority: Debian including 1 source packages (golang-github-hashicorp-go-getter), 2 status rows across 2 suites (bookworm, bullseye): open 2. https://security-tracker.debian.org/tracker/CVE-2022-26945
redhat high — https://access.redhat.com/security/cve/CVE-2022-26945
ubuntu medium CVE-2022-26945 medium priority: Ubuntu including 2 source packages (golang-github-hashicorp-go-getter, golang-github-jesseduffield-go-getter), 20 status rows across 12 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, upstream): ignored 8, needed 8, DNE 2, needs-triage 1, released 1. https://ubuntu.com/security/CVE-2022-26945

Affected software / configurations for CVE-2022-26945

Vendor Product Version Raw CPE
hashicorp go-getter <= 1.5.11 cpe:2.3:a:hashicorp:go-getter:*:*:*:*:*:*:*:*
hashicorp go-getter 2.0.2 cpe:2.3:a:hashicorp:go-getter:2.0.2:*:*:*:*:*:*:*

References for CVE-2022-26945

cvelogic Threat Intelligence