How severe is GHSA-6x6c-w9w9-hv4h?

No CVSS score has been assigned to GHSA-6x6c-w9w9-hv4h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6x6c-w9w9-hv4h?

GHSA-6x6c-w9w9-hv4h affects the following packages: github.com/infracost/infracost (Go). Ecosystems affected: Go.

How do I fix GHSA-6x6c-w9w9-hv4h?

Update github.com/infracost/infracost to 0.10.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6x6c-w9w9-hv4h is resolved across your whole dependency graph.

How do I detect GHSA-6x6c-w9w9-hv4h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/infracost/infracost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6x6c-w9w9-hv4h if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-6x6c-w9w9-hv4h actively exploited in the wild?

No public exploit code has been indexed for GHSA-6x6c-w9w9-hv4h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6x6c-w9w9-hv4h?

GHSA-6x6c-w9w9-hv4h has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6x6c-w9w9-hv4h?

GHSA-6x6c-w9w9-hv4h is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6x6c-w9w9-hv4h published, and has it been updated?

GHSA-6x6c-w9w9-hv4h was published on September 8, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Infracost: Terraform Cloud and registry token disclosure via unvalidated hostnameGHSA-6x6c-w9w9-hv4h

Fix: infracost/infracost#3590

GHSA-6x6c-w9w9-hv4h is a CWE-522 vulnerability in github.com/infracost/infracost. A fix is available for github.com/infracost/infracost — see the affected versions and patch details below.

Also known asCVE-2026-71494GO-2026-6437

Published

Sep 8, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6x6c-w9w9-hv4h.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/infracost/infracost

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

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.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/infracost/infracost`	all versions	0.10.45`go get github.com/infracost/infracost@v0.10.45`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/infracost/infracost, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/infracost/infracost to 0.10.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6x6c-w9w9-hv4h is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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,

O3 Security · Impact-Aware SCA

Is GHSA-6x6c-w9w9-hv4h in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works