{"items":[{"id":"NVI-00007425","kind":"vulnerability","title":"Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs","revision":4,"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-f9f8-rm49-7jv2","CVE-2026-45793"],"plain_summary":"GitHub lists this reviewed advisory for composer/composer, composer/composer, composer/composer. 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-51d472c151cf2a33f7c4b68d33517f8c"],"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},{"summary":"The original advisory lists fixed boundaries 2.9.8 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.10.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","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-07-20T19:12:16.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5cf8b26b0c6b6c25a536c2545f368056"},{"kind":"CVSS","as_of":"2026-07-15T20:54:43.733Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-e00fc1f48b30e23bd15cc1b82f9a24e5"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.021%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63437. Missing scores are unknown.","source_id":"sr-51d472c151cf2a33f7c4b68d33517f8c"}],"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-5cf8b26b0c6b6c25a536c2545f368056","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"},{"id":"sr-db67bb16860156776e150aa9ab0fb52c","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.712Z"},{"id":"sr-e00fc1f48b30e23bd15cc1b82f9a24e5","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45793","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45793","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-51d472c151cf2a33f7c4b68d33517f8c","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-45793","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 2.3.0, < 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 2.0.0, < 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 1.0, < 1.10.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 1.10.28"]}],"null_published_at":"2026-11-07T22:29:23.464Z","source_updated_at":"2026-07-20T19:12:16.000Z","source_disclosed_at":"2026-05-19T16:17:58.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-10-31T21:42:10.712Z"},{"id":"NVI-00007425","kind":"vulnerability","title":"Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f9f8-rm49-7jv2","CVE-2026-45793"],"plain_summary":"GitHub lists this reviewed advisory for composer/composer, composer/composer, composer/composer. 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-51d472c151cf2a33f7c4b68d33517f8c"],"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},{"summary":"The original advisory lists fixed boundaries 2.9.8 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.10.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","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-07-20T19:12:16.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5cf8b26b0c6b6c25a536c2545f368056"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.021%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63437. Missing scores are unknown.","source_id":"sr-51d472c151cf2a33f7c4b68d33517f8c"}],"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-5cf8b26b0c6b6c25a536c2545f368056","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"},{"id":"sr-db67bb16860156776e150aa9ab0fb52c","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.712Z"},{"id":"sr-51d472c151cf2a33f7c4b68d33517f8c","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-45793","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 2.3.0, < 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 2.0.0, < 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-5cf8b26b0c6b6c25a536c2545f368056"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":[">= 1.0, < 1.10.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 1.10.28"]}],"null_published_at":"2026-11-04T10:04:27.926Z","source_updated_at":"2026-07-20T19:12:16.000Z","source_disclosed_at":"2026-05-19T16:17:58.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-10-31T21:42:10.712Z"},{"id":"NVI-00007425","kind":"vulnerability","title":"Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f9f8-rm49-7jv2","CVE-2026-45793"],"plain_summary":"OSV carries this publisher advisory for composer/composer, composer/composer, composer/composer. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.9.8 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.10.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-51d472c151cf2a33f7c4b68d33517f8c"],"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-10-31T12:00:27.000Z","value":"1.021%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.63437. Missing scores are unknown.","source_id":"sr-51d472c151cf2a33f7c4b68d33517f8c"}],"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-db67bb16860156776e150aa9ab0fb52c","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.712Z"},{"id":"sr-51d472c151cf2a33f7c4b68d33517f8c","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-45793","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 1.10.28"]}],"null_published_at":"2026-10-31T23:18:17.292Z","source_updated_at":"2026-07-20T21:26:45.763Z","source_disclosed_at":"2026-05-19T16:17:58.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-10-31T21:42:10.712Z"},{"id":"NVI-00007425","kind":"vulnerability","title":"Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f9f8-rm49-7jv2","CVE-2026-45793"],"plain_summary":"OSV carries this publisher advisory for composer/composer, composer/composer, composer/composer. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.9.8 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.10.28 for composer/composer. Confirm the publisher’s latest guidance.","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"action_type":"vendor_patch","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-db67bb16860156776e150aa9ab0fb52c","url":"https://github.com/advisories/GHSA-f9f8-rm49-7jv2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f9f8-rm49-7jv2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.712Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.3.0; fixed 2.9.8"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.2.28"]},{"certainty":"source_listed","source_ids":["sr-db67bb16860156776e150aa9ab0fb52c"],"technology":"composer/composer","known_exclusions":[],"conditions_summary":"### Summary\n\nComposer leaks the full contents of tokens configured as GitHub OAuth tokens if they do not match Composer's expected format for such tokens to stderr. GitHub has introduced a new format for GitHub Actions GITHUB_TOKEN values. These tokens are validated in the same way by Composer on GitHub Actions. The new format including a `-` (hyphen) fails Composer's validation and leads to disclosure of the GITHUB_TOKEN in logs.\n\nMany widely-used Actions (e.g. `shivammathur/setup-php`) auto-register `GITHUB_TOKEN` into composer's global `auth.json`, so the leak triggers without any unusual user configuration.\n\nGitHub Actions tokens expire when the associated job finishes, and they are scoped to the respective repository only. So in most regular cases the Composer validation, which errors while leaking the token, also immediately ends the job, expiring the token immediately. Tokens expire at the very latest after 6 hours on GitHub-hosted runners. If you use self-hosted runner, expiration is at most 24 hours after creation. The new token format is being rolled out gradually, so not all repositories are affected yet, but will be soon.\n\nClassic `ghp_` PATs are not affected by the reg","public_affected_ranges":["ECOSYSTEM: introduced 1.0; fixed 1.10.28"]}],"null_published_at":"2026-10-31T22:13:14.336Z","source_updated_at":"2026-07-20T21:26:45.763Z","source_disclosed_at":"2026-05-19T16:17:58.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-10-31T21:42:10.712Z"}],"next_cursor":null,"snapshot_revision":"42594"}