dbcve.org
Go GetterApplication · Hashicorp

CVE-2025-8959

HIGH · 7.5 CVSS v3.1 Published 2025-08-15
Fix available
A fix is available. Upgrade to 1.7.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
HashiCorp's go-getter library subdirectory download feature is vulnerable to symlink attacks leading to unauthorized read access beyond the designated directory boundaries. This vulnerability, identified as CVE-2025-8959, is fixed in go-getter 1.7.9.

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 confidence

HashiCorp's go-getter library has a symlink attack vulnerability in its subdirectory download feature (CVE-2025-8959, CVSS 7.5). Attackers can craft malicious symlinks during archive extraction to escape the intended download directory and read files outside the boundary, leading to unauthorized information disclosure.

MitigationUpgrade go-getter library to version 1.7.9 or later to resolve the symlink traversal vulnerability. Review any usage of the subdirectory download feature in dependent applications for potential exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Go GetterApplication
Affected:< 1.7.9

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if go-getter library is in use
    Search your codebase, dependencies, or vendor directories for 'github.com/hashicorp/go-getter' or 'go-getter'. Check go.mod files, vendor manifests, or dependency lock files (go.sum, Gopkg.lock, etc.) for this import path.
    Affected if The go-getter library is present in your dependencies
  2. Determine the installed go-getter version
    Inspect your dependency lock file (go.sum) or vendor directory for the exact version of hashicorp/go-getter. Run 'go list -m all' or check your dependency management tool's output for the version number.
    Affected if The version is lower than 1.7.9 (e.g., 1.7.8, 1.6.x, etc.)
  3. Identify use of subdirectory download feature
    Search your codebase for calls to getter functions that accept a '?archive=subdir' or similar subdirectory parameter, or look for getter client instantiation with subdirectory options enabled. Review any code that constructs getter URLs with subdirectory paths.
    Affected if Your application code uses the subdirectory download feature of go-getter to fetch resources from archives
  4. Verify if getter handles untrusted archives
    Review whether the go-getter library is used to download archives from untrusted or user-controlled sources, or from URLs not under your organization's control.
    Affected if Go-getter downloads archives from untrusted or external sources
  5. Check for symlink usage in downloaded content
    Inspect any archives or repositories your application downloads to see if they contain symbolic links that could point outside the intended download directory.
    Affected if Downloaded archives contain symlinks and are extracted by go-getter

You are affected if your environment uses go-getter library version below 1.7.9 AND utilizes the subdirectory download feature to fetch archives from any source.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.7.9 or later
Fixed in 1.7.9
Interim mitigation

Upgrade go-getter library to version 1.7.9 or later to resolve the symlink traversal vulnerability. Review any usage of the subdirectory download feature in dependent applications for potential exposure.

Recommended fix High confidence

go-getter v1.7.9

  1. Identify all projects or dependencies that use the go-getter library
  2. Run 'go get github.com/hashicorp/[email protected]' or update the go-getter version in your go.mod file to version 1.7.9
  3. Run 'go mod tidy' to update dependencies and remove unused ones
  4. Rebuild and test your application to ensure the upgrade does not break existing functionality
  5. Deploy the updated application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Getter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8959 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8959 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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