CVE-2026-4660 | Go-getter may allow to arbitrary filesystem reads through git operations

HashiCorp’s go-getter library up to v1.8.5 may allow arbitrary file reads on the file system during certain git operations through a maliciously crafted URL. This vulnerability, CVE-2026-4660, is fixed in go-getter v1.8.6. This vulnerability does not affect the go-getter/v2 branch and package.

Published: 2026-04-09 Last update: 2026-04-13 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4660 is rated Low Risk (33.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2026-4660

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-04-10 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4660

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 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:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-4660

GitHub Security Advisory for CVE-2026-4660

GHSA-92mm-2pjq-r785 · Severity: high · Ecosystem: go — HashiCorp's go-getter library may allow arbitrary file reads

OS Trackers for CVE-2026-4660

vendor priority summary link
debian not yet assigned CVE-2026-4660 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-2026-4660
redhat high — https://access.redhat.com/security/cve/CVE-2026-4660
ubuntu medium CVE-2026-4660 medium priority: Ubuntu including 1 source packages (golang-github-hashicorp-go-getter), 6 status rows across 6 suites (bionic, focal, jammy, noble, questing, upstream): needs-triage 6. https://ubuntu.com/security/CVE-2026-4660

Affected software / configurations for CVE-2026-4660

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-4660

cvelogic Threat Intelligence