Skip to content
Fencer Intel
high 7.5

CVE-2026-4660 json

Go-getter may allow to arbitrary filesystem reads through git operations

published 7mo ago modified 14d ago also EUVD-2026-20894 , GHSA-92mm-2pjq-r785 , GO-2026-5058

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/go-getter 1.8.6
  • HashiCorp Tooling 1.8.6
  • Red Hat Red Hat Trusted Artifact Signer 1.3 1780399582
  • golang-github-hashicorp-go-getter Debian 14 1.8.9-1

debian advisories DEBIAN-CVE-2026-4660

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-4660 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-4660 updated cvss 7.5

go-getter: go-getter: Arbitrary file reads via maliciously crafted URL

  • Red Hat Trusted Artifact Signer redhat-user-workloads/rhtap-contract-tenant/ec-v08/cli-v08
    affected: no fix available
  • Red Hat Trusted Artifact Signer 1.3 rhtas/client-server-rhel9 1780399582
    fixed: vendor fix RHSA-2026:24478
  • Red Hat OpenShift Container Platform 4 redhat-user-workloads/ocp-art-tenant/art-images
    not affected: component not present
  • Red Hat Trusted Artifact Signer redhat-user-workloads/rhtap-contract-tenant/ec-v06/cli-v06
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/go-getter
<1.8.6
1.8.6

Affected products

  • HashiCorp Tooling
  • Red Hat Red Hat Trusted Artifact Signer 1.3
  • Red Hat Red Hat OpenShift Container Platform 4
  • Red Hat Red Hat Trusted Artifact Signer

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.