What is CVE-2026-71494?

CVE-2026-71494 is a medium-severity security vulnerability in github.com/infracost/infracost (go), affecting versions < 0.10.45. It is fixed in 0.10.45.

Which versions of github.com/infracost/infracost are affected by CVE-2026-71494?

github.com/infracost/infracost (go) versions < 0.10.45 is affected.

Is there a fix for CVE-2026-71494?

Yes. CVE-2026-71494 is fixed in 0.10.45. Upgrade to this version or later.

Is CVE-2026-71494 exploitable, and should I be worried?

Whether CVE-2026-71494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-71494 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-71494?

Upgrade github.com/infracost/infracost to 0.10.45 or later.

CVE-2026-71494 in github.com/infracost/infracost

Q: Which versions of github.com/infracost/infracost are affected by CVE-2026-71494?

github.com/infracost/infracost (go) versions < 0.10.45 is affected.

Q: Is there a fix for CVE-2026-71494?

Yes. CVE-2026-71494 is fixed in 0.10.45. Upgrade to this version or later.

Q: Is CVE-2026-71494 exploitable, and should I be worried?

Whether CVE-2026-71494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-71494 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-71494?

Upgrade github.com/infracost/infracost to 0.10.45 or later.

Summary

Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname

Workarounds

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

Impact

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.

Affected versions

github.com/infracost/infracost (< 0.10.45)

Security releases

github.com/infracost/infracost → 0.10.45 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in v0.10.45 (#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

Installed via the official script, a package manager, or the latest Docker tag: upgrade to v0.10.45 (or later) to receive the fix.
Pinned to a specific version or image digest: bump to v0.10.45.

Frequently Asked Questions

What is CVE-2026-71494? CVE-2026-71494 is a medium-severity security vulnerability in github.com/infracost/infracost (go), affecting versions < 0.10.45. It is fixed in 0.10.45.
Which versions of github.com/infracost/infracost are affected by CVE-2026-71494? github.com/infracost/infracost (go) versions < 0.10.45 is affected.
Is there a fix for CVE-2026-71494? Yes. CVE-2026-71494 is fixed in 0.10.45. Upgrade to this version or later.
Is CVE-2026-71494 exploitable, and should I be worried? Whether CVE-2026-71494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-71494 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-71494? Upgrade github.com/infracost/infracost to 0.10.45 or later.