Composer is a dependency Manager for the PHP language. Prior to 2.2.29 and 2.10.2, when Composer is run with -vvv debug verbosity, it could print a credential embedded in the username slot of a repository or package URL, such as a GitHub Personal Access Token in https://TOKEN@host/, to debug output because AuthHelper, Url::sanitize, and ProcessExecutor did not sanitize username-only URL credentials. This issue is fixed in versions 2.2.29 and 2.10.2.
CVE-2026-59947
This medium-severity CVE scores 4.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(low)
- EPSS
- —
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 8, 2026
Advisory Details (5)
Auto-updated Jul 8, 2026URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure) · Advisory · composer/composer · GitHub
https://github.com/composer/composer/security/advisories/GHSA-g6xq-892h-64w32.2.29
Patch available: composer/composer 2.2.29
https://github.com/composer/composer/releases/tag/2.2.292.10.2
Patch available: composer/composer 2.10.2
https://github.com/composer/composer/releases/tag/2.10.2commit 8887ad76fbd8 (composer/composer)
Patch available: composer/composer 2.10.2 (contains commit 8887ad76fbd8)
https://github.com/composer/composer/commit/8887ad76fbd830cb1861a2b1fd8ead78ed1fa1eccommit 6bd66874ae52 (composer/composer)
Patch available: composer/composer 2.2.29 (contains commit 6bd66874ae52)
https://github.com/composer/composer/commit/6bd66874ae523ecb69aca5964487a0cdfda03ef8Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 19:46 UTCEG score recompute
- 2026-07-08 19:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 94%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-59947?
When was CVE-2026-59947 disclosed?
What is the CVSS score of CVE-2026-59947?
How do I remediate CVE-2026-59947?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59947
Is Your Infrastructure Affected by CVE-2026-59947?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.