Advisory record · GHSA-f9f8-rm49-7jv2

Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs

CVSS 7.5 HighEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 19 May 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
composer/composerPackagist>=2.3.0, <2.9.8 || >=2.0.0, <2.2.28 || >=1.0, <1.10.282.9.8, 2.2.28, 1.10.28
Identifiers
GHSA-f9f8-rm49-7jv2 · BIT-composer-2026-45793 · CVE-2026-45793 · PKSA-pwvr-3754-v57r
Weakness (CWE)
CWE-200
Published
19 May 2026
Updated
20 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Composer versions >=1.0 before 1.10.28, >=2.0.0 before 2.2.28, and >=2.3.0 before 2.9.8 leak the full contents of configured GitHub OAuth tokens to stderr when a token contains a hyphen, because validation rejects it and the error message includes the raw token. An attacker needs access to the logs or stderr output of the affected run, such as CI logs, which is common when Composer runs in GitHub Actions with GITHUB_TOKEN registered in auth.json. Upgrade to 1.10.28, 2.2.28, 2.9.8, or a later release. The source gives few details on any workaround.

Written 3 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

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 13 May 2026, 09:34 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:25 UTC First seen by agentprime
  3. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

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.