CVE-2026-4660
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHashiCorp’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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe go-getter library up to v1.8.5 contains an arbitrary file read vulnerability where maliciously crafted URLs during git operations can read files from the filesystem outside the intended directory. This allows unauthenticated remote attackers to potentially access sensitive files via specially constructed getter URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify go-getter in dependenciesRun 'go list -m all' or inspect go.mod/go.sum files to find go-getterAffected if go-getter appears in the dependency list at version 1.8.5 or below
-
Check installed go-getter versionRun 'go list -m github.com/hashicorp/go-getter' or check the version in go.modAffected if Version is 1.8.5 or lower, or no version is shown (indicating an unpatched version)
-
Determine if application performs git operations with URLsReview code for usage of go-getter functions that handle git URLs (Get, GetContext, or custom getter setup)Affected if The application uses go-getter to fetch from git repositories via URLs
-
Check if v2 branch is in useSearch for 'github.com/hashicorp/go-getter/v2' in dependency files or code importsAffected if go-getter/v2 is NOT imported; only go-getter v1.x is used (v2 is unaffected)
-
Verify git executable is availableConfirm git is installed on systems where go-getter runs (required for git-based URL handling)Affected if git is installed and go-getter v1.x with URL-based git operations is in use
Affected if go-getter v1.8.5 or lower is present AND the application uses it to fetch from git URLs; not affected if v1.8.6+ or the v2 branch is used instead.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade go-getter to v1.8.6 or later. Review all usage of go-getter in applications to ensure no untrusted URLs can be supplied to getter operations.
go-getter v1.8.6
- Identify all projects and dependencies that use the go-getter library (github.com/hashicorp/go-getter) version 1.8.5 or below
- Update the go-getter dependency to version 1.8.6 or later in your dependency management system (e.g., go.mod for Go projects)
- Run dependency update commands (e.g., go get github.com/hashicorp/[email protected] or go mod tidy)
- Rebuild and recompile all affected applications
- Redeploy the updated applications to production environments
- Verify the fix by testing that git operations through go-getter no longer allow arbitrary file reads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4660 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data