Skip to main content
VulnerabilityPublished

CVE-2026-14978: HashiCorp go-slug · Improper Handling of Unicode Encoding

Affects HashiCorp go-slugSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
HashiCorpgo-slugAffected
  • >=0.4.0 <=0.18.2
Fixed in–

CPE configurations (2)

  • cpe:2.3:a:hashicorp:go_slug:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:hashicorp:go_slug:0.18.2:*:*:*:*:*:*:*

AI-suggested

Until a fix is available, users should exercise caution with local file handling and review .terraformignore configurations carefully.

Description

HashiCorp go-slug versions 0.4.0 through 0.18.2 contain a vulnerability where improper handling of Unicode normalization during path matching can allow a local attacker to bypass .terraformignore exclusions. This may result in sensitive files being included in Terraform slug uploads.

References

Community reviews

Loading reviews…