CVE-2026-71494: Infracost Terraform Cloud And Registry Token Vulnerability
MODERATECVE-2026-71494 is a MODERATE terraform cloud and registry token vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Infracost libraries in the Go ecosystem. The issue involves terraform cloud and registry token disclosure via unvalidated hostname. Remediation is available by upgrading affected packages to version 0.10.45.
CVE-2026-71494 at a Glance
How to Fix CVE-2026-71494
To remediate this vulnerability, upgrade all affected Infracost dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/infracost/infracost to 0.10.45
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/infracost/infracost
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-71494, inspect your project dependencies for Infracost:
inspect dependencies for github.com/infracost/infracost
Analyze the terminal output to locate any version of Infracost in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.10.45), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Infracost, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-71494 Affected Infracost Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/infracost/infracost
|
Go |
< 0.10.45
|
0.10.45
|
References
Frequently Asked Questions
What is CVE-2026-71494?
Which Infracost versions are affected?
What version fixes CVE-2026-71494?
Is github.com/infracost/infracost affected?
What CWE is associated with CVE-2026-71494?
How can I check Go dependencies for CVE-2026-71494?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6x6c-w9w9-hv4h",
"modified" : "2026-09-08T18:14:12Z",
"published" : "2026-09-08T18:14:12Z",
"aliases" : [ "CVE-2026-71494" ],
"summary" : "Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname",
"details" : "### Impact\n\nSensitive information exposure in the Infracost Terraform Cloud/Enterprise integration. Several code paths attached a configured secret token to a request whose host was taken straight from the scanned Terraform, with no check that the host was the trusted endpoint. \n\nThe condition that matters is whether a Terraform Cloud/Enterprise (or registry) token is present in the run: if one is, the injected hostname can disclose it. Impact therefore depends on the trigger. Under `on: pull_request` (the only configuration in Infracost's documentation) fork pull requests run without secrets, so no token is present. It only reaches token disclosure under `pull_request_target`, a same-repository pull request, or another CI setup that provides the token alongside untrusted Terraform, and exploiting an untrusted fork pull request also typically needs a maintainer to approve the workflow run. The patch scopes the token to the trusted host regardless of trigger.\n\n### Patches\n\nFixed in `v0.10.45` ([#3590](https://github.com/infracost/infracost/pull/3590)) by attaching a token only when the destination host matches the configured trusted host; otherwise Infracost refuses to send it and skips remote variable loading\n - Installed via the official script, a package manager, or the `latest` Docker tag: upgrade to `v0.10.45` (or later) to receive the fix.\n - Pinned to a specific version or image digest: bump to `v0.10.45`.\n\n### Workarounds\n\nNo full fix without upgrading. To limit exposure: use `on: pull_request` rather than `pull_request_target`, pin `organization`, `workspace`, and `host` in Infracost config so the `.tf` hostname is ignored, and keep Terraform Cloud and registry tokens out of runs that process untrusted pull request content.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/infracost/infracost"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.10.45"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/infracost/infracost/security/advisories/GHSA-6x6c-w9w9-hv4h"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-71494"
}, {
"type" : "WEB",
"url" : "https://github.com/infracost/infracost/pull/3590"
}, {
"type" : "WEB",
"url" : "https://github.com/infracost/infracost/commit/3d24c757f5e4e60c7259f1b89ad7ceaabcfca86f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/infracost/infracost"
}, {
"type" : "WEB",
"url" : "https://github.com/infracost/infracost/releases/tag/v0.10.45"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-522" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-08T18:14:12Z",
"nvd_published_at" : "2026-08-21T18:16:50Z"
}
}