cve.bz

CVE-2026-4660 hashicorp tooling: Path traversal

7.5 highEPSS 0.6%Fix available

High (7.5) in hashicorp tooling. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/hashicorp/go-getter 1.8.6.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-4660 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-4660?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-4660?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-4660 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
HashiCorp Toolingbefore 1.8.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-92mm-2pjq-r785Gogithub.com/hashicorp/go-getter<1.8.61.8.6
GO-2026-5058Gogithub.com/hashicorp/go-getter<1.8.61.8.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12golang-github-hashicorp-go-getterno fix listedDEBIAN-CVE-2026-4660
Debian14golang-github-hashicorp-go-getter1.8.9-1DEBIAN-CVE-2026-4660
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 2 moregolang-github-hashicorp-go-getterno fix listedUBUNTU-CVE-2026-4660
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
Alpaquitastreamgrype0.114.0-r0BELL-CVE-2026-4660

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat Trusted Artifact Signer 1.3rhtas/client-server-rhel9:1780399582Fixed 2026-06-08RHSA-2026:24478
Red Hat OpenShift Container Platform 4redhat-user-workloads/art-imagesNot affected
Red Hat Trusted Artifact Signerredhat-user-workloads/cli-v06Not affected
Red Hat Trusted Artifact Signerredhat-user-workloads/cli-v08Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-4660.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • gouldnicholas/CVE-2026-4660-PoC Harbor Check: matches CVE 1 star, Shell, created
    PoC for CVE-2026-4660: arbitrary file read via git checkout in hashicorp/go-getter

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON