# CVE-2026-71494: Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname

> Attackers can steal Terraform Cloud or registry tokens by directing requests to malicious hosts via unvalidated hostnames in CI workflows.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-6x6c-w9w9-hv4h, GO-2026-6437

## What is CVE-2026-71494?

CVE-2026-71494 is a medium-severity vulnerability in infracost, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Infracost provides cloud cost intelligence for engineers, AI coding agents, and CI/CD. Prior to 0.10.45, internal/hcl/remote_variables_loader.go and related Terraform Cloud, remote-plan, and Terragrunt registry request paths can attach a configured Terraform Cloud or registry token to a destination hostname derived from untrusted Terraform input without confirming that it is the configured trusted host. When a CI run provides a token while scanning attacker-controlled Terraform, including pull_request_target or a same-repository pull request, an attacker can direct the request to an attacker-controlled host and disclose the token. Standard fork pull_request workflows without secrets are not exposed. This issue is fixed in version 0.10.45.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

3 open source packages ship an affected version, including github.com/infracost/infracost.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/infracost/infracost` | Go | All versions | 0.10.45 |
| `github.com/infracost/infracost` | Go | All versions | 0.10.45 |
| `github.com/infracost/infracost` | Go | All versions | 0.10.45 |

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

Upgrade github.com/infracost/infracost to 0.10.45 or later.

## Is CVE-2026-71494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71494 is a medium-severity vulnerability in infracost, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71494 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/infracost/infracost (Go): affected all versions; fixed in 0.10.45
- github.com/infracost/infracost (Go): affected all versions; fixed in 0.10.45
- github.com/infracost/infracost (Go): affected all versions; fixed in 0.10.45

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-71494/ (Markdown: https://insights.sbomify.com/CVE-2026-71494/index.md)
```

## Sources

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

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