CVE-2026-71494

MediumCVSS 5.9

Published: 21/08/2026(UTC)Updated: 21/08/2026(UTC)Translated: 22/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.37%

30th percentile - higher than 30% of all known CVEs

Summary

Infracost 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.

Risk Assessment

Disclosure of Terraform Cloud or registry tokens may allow an attacker unauthorized access to cloud infrastructure.

Recommendation

It is recommended to upgrade Infracost to version 0.10.45 or later, which includes a fix.

Other vulnerabilities in Infracost

CVE-2026-71493Medium
Prior to version 0.10.45, Infracost had a vulnerability where the template functions readFile, pathExists, isDir, and matchPaths did not resolve intermediate directory symlinks. A repository could contain a path such as evil/file where evil points outside the checkout, causing os.ReadFile and related operations to follow the symlink and read runner-accessible files. The resulting content could be rendered into generated configuration and surfaced through the Infracost dashboard or pull request comment, with greater impact in workflows that provide repository secrets.

Original NVD description (English source)

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.