Answer in brief
CVE-2026-71494 records a Medium severity (CVSS 5.9) vulnerability in Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname. The current sources do not mark it as known exploited. The current feed maps infracost/infracost (generic), github.com/infracost/infracost (go), github.com/infracost/infracost (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps infracost/infracost (generic), github.com/infracost/infracost (go), github.com/infracost/infracost (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| infracost/infracostgeneric | <0.10.45 | 0.10.45 |
| github.com/infracost/infracostgo | <0.10.45 | 0.10.45 |
| github.com/infracost/infracostgo | >=0 <0.10.45 | 0.10.45 |
Published upstream
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.