Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname

CVE-2026-71494GHSA-6x6c-w9w9-hv4h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/infracost/infracost 0.10.45), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-71494: 0.50% estimated exploitation activity in the next 30 days; percentile 42.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: pullrequest (the only configuration in Infracost's documentation) fork pull requests run without secrets, so no token is present. It only reaches token disclosure under pullrequesttarget, 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. Patches Fixed in v0.10.45 (#3590) by…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-6x6c-w9w9-hv4h

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6437

  4. Revision 1 · created ·

    Published from osv record GHSA-6x6c-w9w9-hv4h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71494

Advisory: Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname
IDs: CVE-2026-71494, GHSA-6x6c-w9w9-hv4h
Record: https://patchnext.com/advisories/cve-2026-71494 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/infracost/infracost 0.10.45. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/infracost/infracost: affected < 0.10.45; fixed in 0.10.45

## Suggested inspection (read-only)
- Go github.com/infracost/infracost: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/infracost/infracost.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6x6c-w9w9-hv4h (OSV record GHSA-6x6c-w9w9-hv4h lists affected ranges: Go github.com/infracost/infracost >=0 <0.10.45 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6437 (OSV record GO-2026-6437 lists affected ranges: Go github.com/infracost/infracost >=0 <0.10.45 (fixed))
- Verified: https://github.com/advisories/GHSA-6x6c-w9w9-hv4h (GitHub-reviewed advisory GHSA-6x6c-w9w9-hv4h lists affected ranges: Go github.com/infracost/infracost >=0 <0.10.45)

Commands are suggestions: review each one before running it.

Loading voting…