# CVE-2026-14978: Unicode normalization mismatch in go-slug ignore pattern matching may bypass intended file exclusions

> A local attacker can bypass Terraform ignore rules via Unicode normalization flaws, exposing sensitive files in slug uploads.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-92x3-5h48-mfhx

## What is CVE-2026-14978?

CVE-2026-14978 is a medium-severity vulnerability in HashiCorp go-slug, published on 19 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

HashiCorp go-slug 0.4.0 through 0.18.2 could allow a local attacker to bypass .terraformignore exclusions and cause sensitive files to be included in Terraform slug uploads due to improper handling of Unicode normalization during path matching.

Weakness: CWE-176 (Improper Handling of Unicode Encoding)

## Which versions are affected by CVE-2026-14978?

It affects 1 product.


Products: Hashicorp Go-Slug.

## How do I fix CVE-2026-14978?

No fix has been published for CVE-2026-14978 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14978 being exploited?

There is no known exploitation of CVE-2026-14978 in the wild and no public exploit code.

## Other vulnerabilities in HashiCorp go-slug

- [CVE-2025-0377](https://insights.sbomify.com/CVE-2025-0377/): HashiCorp go-slug Vulnerable to Zip Slip Attack (high 7.5)
- [CVE-2020-29529](https://insights.sbomify.com/CVE-2020-29529/): Unsafe tar unpacking in HashiCorp go-slug (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14978 and fix it if it is affected.

What it is: CVE-2026-14978 is a medium-severity vulnerability in HashiCorp go-slug, published on 19 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-14978 in the wild and no public exploit code.

Affected product: HashiCorp go-slug. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14978/ (Markdown: https://insights.sbomify.com/CVE-2026-14978/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14978
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14978
- OSV: https://osv.dev/vulnerability/CVE-2026-14978

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14978/
Summaries are generated and may contain mistakes; the official description above is the record.