CVE-2026-4660
A public proof of concept exists; no exploitation attested.
- Published2026-04-09
- Fixed in1.8.6
- WeaknessCWE-200 · CWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-04-0914:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-4660?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-4660?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.8 | < 1.8.6 | 1.8.6 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Red Hat Security Advisory: RHTAS 1.3.5 - Red Hat Trusted Artifact Signer Release
Fix
- Update hashicorp/go-getter to 1.8.6
- Vendor fix Red Hat Product Security RHSA-2026:24478 · 1 productRed Hat Trusted Artifact Signer simplifies cryptographic signing and verifying of software artifacts such as container images, binaries and source code changes. It is a self-managed on-premise deployment of the Sigstore project available at https://sigstore.dev Platform Engineers, Software Develop…
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-04-09
- OpenCVESSVC decisionnone—
- CNACVSS 3.17.5read 2026-10-23
- CNAweakness (CWE)CWE-200, CWE-22read 2026-10-23
- FIRST EPSSEPSS score0.5 %2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2026-04-09
- Last Modified
- 2026-07-15
- NVD status
- Awaiting Analysis
Frequently asked questions
What is CVE-2026-4660?
Is CVE-2026-4660 actively exploited?
What is the CVSS score for CVE-2026-4660?
Running hashicorp/go-getter? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.