# Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname Advisory record · `GHSA-6x6c-w9w9-hv4h` - **Identifiers:** `GHSA-6x6c-w9w9-hv4h` · `CVE-2026-71494` · `GO-2026-6437` - **State:** Confirmed - **Severity:** CVSS 5.9 Medium - **Critical:** No - **Weakness (CWE):** [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 8 Sept 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 8 Sept 2026, 18:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/infracost/infracost` (Go): affected `<0.10.45`; fixed in `0.10.45` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Infracost, the Go package github.com/infracost/infracost, versions before 0.10.45 can attach a configured Terraform Cloud or registry token to a request sent to a hostname taken from scanned Terraform, without checking that the host is trusted. An attacker who can supply Terraform to a run that also has a token present, such as under pull_request_target or a same-repository pull request, could receive that token. Upgrade to 0.10.45 or later, which sends the token only to the trusted host. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 5.9 Medium, CVSS 4.0: `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`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0050, the 43rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6x6c-w9w9-hv4h) ## Sources - [GitHub Advisory Database: GHSA-6x6c-w9w9-hv4h](https://github.com/advisories/GHSA-6x6c-w9w9-hv4h) - [OSV: GHSA-6x6c-w9w9-hv4h](https://osv.dev/vulnerability/GHSA-6x6c-w9w9-hv4h) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .