CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-15
NOTABLECVE-2026-45793updatedNATOA2vulnerability

CVE-2026-45793, PHP Composer: GitHub Actions and GitHub App installation tokens printed in full to CI job logs when GitHub's new token format failed validation (CVSS 7.5)

Composer printed GitHub Actions tokens into CI logs once GitHub's new token format arrived; fixed in 2.9.8 and 2.2.28

Analysis

Composer validates configured GitHub tokens against an allowed character set in Composer\IO\BaseIO::loadConfiguration(); GitHub's new structured format for GitHub App installation tokens contains a hyphen, fails that check, and the resulting exception prints the full token to stderr, which CI captures in the job log, while GitHub Actions' secret masker may not redact it because the message is wrapped or framed (Packagist, 2026-05-13). Any workflow that configures a GitHub App installation token, including the auto-injected GITHUB_TOKEN, into Composer's auth and then runs any Composer command hits it, and actions such as shivammathur/setup-php register GITHUB_TOKEN automatically, so no unusual configuration is needed (Packagist, 2026-05-13). The advisory's header rates CVE-2026-45793 High 7.5 while its own text calls the severity medium, and it lists Composer from 2.3.0 before 2.9.8, from 2.0.0 before 2.2.28 and from 1.0 before 1.10.28 as affected, fixed in 2.9.8, 2.2.28 and 1.10.28 (Composer, 2026-05-13). CISA's Known Exploited Vulnerabilities catalogue did not list it as of 2026-10-21 (CISA KEV catalog, 2026-10-21).

The exposure window depends on the token: a hosted-runner GITHUB_TOKEN expires when the job ends or after six hours, and the error usually fails the job and expires it at once; on self-hosted runners it can stay valid for up to 24 hours after issuance; and tokens from actions/create-github-app-token or another GitHub App last up to an hour by default and can carry permissions broader than the workflow's own permissions: declaration (Packagist, 2026-05-13). GitHub rolled back the token change on 2026-05-13 at 14:30 UTC and planned to restart the rollout on 2026-05-18 after 14:00 UTC (Packagist, 2026-05-13).

Cited evidence

The new format fails Composer’s validation, leading to an error message that exposes the full token contents to stderr.

Any workflow that configures a GitHub App installation token (including the workflow's auto-injected GITHUB_TOKEN) into Composer's auth and then runs any Composer command will hit it.

Usually the error leaking the token will also fail the job and immediately expire the token.

Packagist 2026-05-13

Updates1

Correction

The leak was not tied to package-resolution errors: GitHub's new format for GitHub App installation tokens contains a hyphen, fails Composer's character validation when its configuration loads, and the exception prints the full token to stderr, so any workflow with such a token in Composer's auth hit it on the default path, including the auto-injected GITHUB_TOKEN (Packagist, 2026-05-13). Classic ghp_ personal access tokens are not affected by the validation bug itself, though the advisory notes the same leak applies to any future credential that fails validation (Composer, 2026-05-13). Packagist's relevant permission point is that App tokens can carry permissions broader than the workflow's own permissions: declaration, not that every GITHUB_TOKEN can write workflow files (Packagist, 2026-05-13).

The exposure was bounded: hosted-runner tokens usually expired with the failing job, self-hosted runner tokens stay valid for up to 24 hours and App tokens for up to an hour, and GitHub rolled the format change back on 2026-05-13 before planning a new rollout from 2026-05-18 (Packagist, 2026-05-13). Neither the Packagist post nor the advisory mentions Mini Shai-Hulud or exploitation; the advisory rates the flaw High 7.5, fixed in 2.9.8, 2.2.28 and 1.10.28 (Composer, 2026-05-13).

Sources3

Revision history

  1. Published 2026-05-15-58b94fbd
  2. Correction 2026-10-21T1148Z-audit

    Composer's token leak was triggered on the default path by GitHub's new hyphenated installation-token format failing Composer's validation when it loaded its configuration, not by package-resolution errors, and it concerned GITHUB_TOKEN and GitHub App installation tokens rather than personal access tokens. Hosted-runner tokens usually expired with the failing job, self-hosted runner tokens stay valid for up to 24 hours and App tokens for up to an hour, and GitHub rolled the format change back on 2026-05-13. No source links the bug to Mini Shai-Hulud, and the advisory rates it High 7.5 with fixes in 2.9.8, 2.2.28 and 1.10.28.

    Changed: affected_products body classification cves entities evidence headline kind sources sourcing_note summary tags techniques title

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.