CVE-2026-14978
Reported by ibm · Published August 19, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| vault-fips-2.0 | Chainguard | 2.0.4-r4 |
| terraform-mcp-server | Chainguard | 1.3.0-r3 |
| opentofu-1.12 | Chainguard | 1.12.6-r6, 1.12.6-r5 |
| opentofu-1.10 | Wolfi | 1.10.10-r20 |
| opentofu-1.9 | Chainguard | 1.9.4-r30 |
| opentofu-1.11 | Chainguard | 1.11.14-r6, 1.11.14-r5 |
| vault-fips-1.21 | Chainguard | 1.21.4-r18 |
| vault-2.0 | Chainguard | 2.0.4-r5 |
| terraform-ls | Chainguard | 0.39.0-r5 |
| opentofu-fips-1.12 | Chainguard | 1.12.6-r6 |
| vault-fips-2.1 | Chainguard | 2.1.0-r3 |
| opentofu-fips-1.10 | Chainguard | 1.10.10-r16 |
16 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| HashiCorp | go-slug | 0.4.0 |
| chainguard | vault-fips-2.0 | 0 |
| chainguard | terraform-mcp-server | 0 |
| chainguard | opentofu-1.12 | 0, 0 |
| wolfi | opentofu-1.10 | 0 |
| chainguard | opentofu-1.9 | 0 |
| chainguard | opentofu-1.11 | 0, 0 |
| chainguard | vault-fips-1.21 | 0 |
| chainguard | vault-2.0 | 0 |
| chainguard | terraform-ls | 0 |
| chainguard | opentofu-fips-1.12 | 0 |
| chainguard | vault-fips-2.1 | 0 |
| chainguard | opentofu-fips-1.10 | 0 |
| wolfi | opentofu-1.11 | 0, 0 |
| chainguard | opentofu-1.10 | 0 |
| chainguard | opentofu-fips-1.9 | 0 |
| HashiCorp | go-slug | 0.4.0 |
| wolfi | opentofu-1.9 | 0 |
| chainguard | vault-2.1 | 0 |
| wolfi | terraform-mcp-server | 0 |
…and 9 more
Timeline
- Aug 19, 2026 CVE Published
- Aug 20, 2026 CVE Updated
- Aug 22, 2026 Coalition ESS Score
- Aug 24, 2026 EPSS Score (7 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-14978
vulnetix vdb fixes CVE-2026-14978
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-14978/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart