{"items":[{"id":"NVI-00013960","kind":"vulnerability","title":"Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-6x6c-w9w9-hv4h","CVE-2026-71494"],"plain_summary":"GitHub lists this reviewed advisory for github.com/infracost/infracost. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1b53f039cd0f2fe0d0121386e0269ed2"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-14T19:10:00.297Z","value":"5.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5772aef1dd5ada431d25c5e16dc354ae"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.500%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.42861. Missing scores are unknown.","source_id":"sr-1b53f039cd0f2fe0d0121386e0269ed2"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-281a80aaa071489d38c334be8572ac6c","url":"https://github.com/advisories/GHSA-6x6c-w9w9-hv4h","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6x6c-w9w9-hv4h","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"},{"id":"sr-5772aef1dd5ada431d25c5e16dc354ae","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-71494","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-71494","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T15:08:07.832Z"},{"id":"sr-1b53f039cd0f2fe0d0121386e0269ed2","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-71494","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.861Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-281a80aaa071489d38c334be8572ac6c"],"technology":"github.com/infracost/infracost","known_exclusions":[],"conditions_summary":"### Impact\n\nSensitive 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. \n\nThe 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.\n\n### Patches\n\nFixed 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 s","public_affected_ranges":["< 0.10.45"]}],"null_published_at":"2026-11-08T19:53:44.059Z","source_updated_at":"2026-09-08T18:14:12.000Z","source_disclosed_at":"2026-09-08T18:14:12.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-02T02:20:31.767Z"},{"id":"NVI-00013960","kind":"vulnerability","title":"Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6x6c-w9w9-hv4h","CVE-2026-71494"],"plain_summary":"GitHub lists this reviewed advisory for github.com/infracost/infracost. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1b53f039cd0f2fe0d0121386e0269ed2"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.500%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.42861. Missing scores are unknown.","source_id":"sr-1b53f039cd0f2fe0d0121386e0269ed2"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-281a80aaa071489d38c334be8572ac6c","url":"https://github.com/advisories/GHSA-6x6c-w9w9-hv4h","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6x6c-w9w9-hv4h","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"},{"id":"sr-1b53f039cd0f2fe0d0121386e0269ed2","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-71494","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.861Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-281a80aaa071489d38c334be8572ac6c"],"technology":"github.com/infracost/infracost","known_exclusions":[],"conditions_summary":"### Impact\n\nSensitive 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. \n\nThe 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.\n\n### Patches\n\nFixed 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 s","public_affected_ranges":["< 0.10.45"]}],"null_published_at":"2026-11-07T14:01:58.719Z","source_updated_at":"2026-09-08T18:14:12.000Z","source_disclosed_at":"2026-09-08T18:14:12.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-02T02:20:31.767Z"},{"id":"NVI-00013960","kind":"vulnerability","title":"Infracost: Terraform Cloud and registry token disclosure via unvalidated hostname","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6x6c-w9w9-hv4h","CVE-2026-71494"],"plain_summary":"GitHub lists this reviewed advisory for github.com/infracost/infracost. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-281a80aaa071489d38c334be8572ac6c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-281a80aaa071489d38c334be8572ac6c","url":"https://github.com/advisories/GHSA-6x6c-w9w9-hv4h","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6x6c-w9w9-hv4h","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-281a80aaa071489d38c334be8572ac6c"],"technology":"github.com/infracost/infracost","known_exclusions":[],"conditions_summary":"### Impact\n\nSensitive 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. \n\nThe 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.\n\n### Patches\n\nFixed 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 s","public_affected_ranges":["< 0.10.45"]}],"null_published_at":"2026-11-02T10:00:37.192Z","source_updated_at":"2026-09-08T18:14:12.000Z","source_disclosed_at":"2026-09-08T18:14:12.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:20:31.767Z"}],"next_cursor":null,"snapshot_revision":"42594"}