CVE-2026-71494: Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname
Sensitive 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.
The 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.
References
- github.com/advisories/GHSA-6x6c-w9w9-hv4h
- github.com/infracost/infracost/commit/3d24c757f5e4e60c7259f1b89ad7ceaabcfca86f
- github.com/infracost/infracost/pull/3590
- github.com/infracost/infracost/releases/tag/v0.10.45
- github.com/infracost/infracost/security/advisories/GHSA-6x6c-w9w9-hv4h
- nvd.nist.gov/vuln/detail/CVE-2026-71494
Code Behaviors & Features
Detect and mitigate CVE-2026-71494 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →