CVE-2026-71493

MediumCVSS 5.9

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

Exploitation Probability (EPSS)

Low risk

0.43%

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

Summary

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.

Risk Assessment

An attacker could access sensitive files accessible to the process running Infracost, including potentially repository secrets, leading to data confidentiality breach and privilege escalation.

Recommendation

Immediately upgrade Infracost to version 0.10.45 or later, which includes a fix for this vulnerability.

Other vulnerabilities in Infracost

CVE-2026-71494Medium
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.

Original NVD description (English source)

Infracost provides cloud cost intelligence for engineers, AI coding agents, and CI/CD. Prior to 0.10.45, the readFile, pathExists, isDir, and matchPaths template functions in internal/config/template/parser.go use a lexical filepath.Rel check and a leaf-only os.Lstat check that do not resolve an intermediate directory symlink. A repository can 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 is rendered into generated configuration and can be surfaced through the Infracost dashboard or pull request comment, with greater impact in workflows that provide repository secrets. This issue is fixed in version 0.10.45.