LiveActive security incident?Get immediate response
CVE Record

CVE-2026-4660: Go-getter may allow to arbitrary filesystem reads through git operations

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-4660 is a high-severity information disclosure flaw in HashiCorp go-getter. A malicious URL used in certain git operations may let an attacker read files from the affected system. The confirmed fix is go-getter v1.8.6; go-getter/v2 is stated as unaffected.

Executive priority

Prioritize remediation where internet-facing workflows accept repository or module URLs. The issue is confidentiality-focused, but arbitrary file reads can expose secrets, tokens, or configuration files that enable wider compromise.

Technical view

HashiCorp go-getter through v1.8.5 may allow arbitrary filesystem reads via crafted URLs during some git operations. The CVSS 3.1 score is 7.5, reflecting network reachability, low complexity, no privileges, no user interaction, and high confidentiality impact only.

Likely exposure

Exposure is most likely where software imports go-getter v1.x through v1.8.5 and accepts untrusted or user-controlled git source URLs. Systems using go-getter/v2 are not affected per the source bundle.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation status should be treated as unconfirmed. Risk is driven by confidentiality impact if crafted URLs reach vulnerable git retrieval paths.

Researcher notes

The bundle does not include detailed root-cause mechanics, proof-of-concept material, or complete downstream product impact. Keep analysis scoped to go-getter v1.x through v1.8.5, crafted URLs, and git operations unless vendor advisories add detail.

Mitigation direction

  • Upgrade HashiCorp go-getter v1.x to v1.8.6 or later.
  • Confirm go-getter/v2 users are actually importing the unaffected v2 package.
  • Restrict untrusted source URLs reaching go-getter git operations.
  • Check HashiCorp and downstream vendor advisories for product-specific guidance.
  • Apply relevant downstream vendor updates, including Red Hat advisories where applicable.

Validation and detection

  • Review SBOMs and lockfiles for github.com/hashicorp/go-getter versions through v1.8.5.
  • Identify code paths that pass user-controlled URLs into go-getter git operations.
  • Verify production builds include go-getter v1.8.6 or unaffected v2 package.
  • Check container images and vendored dependencies for stale go-getter copies.
  • Review vendor advisories for downstream package status before closing exposure.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-4660 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6HashiCorp
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-4660Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPgo-getter: go-getter: Arbitrary file reads via maliciously crafted URL
other:Red Hat severity ratingcvssV3_1
  • 2026-04-09T15:01:32.667Z: Reported to Red Hat.
  • 2026-04-09T13:47:46.953Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HashiCorpTooling0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.