CVE-2026-59947

MEDIUMPre-NVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

URL-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-64w3
github_release Patch Available

2.2.29

Patch available: composer/composer 2.2.29

https://github.com/composer/composer/releases/tag/2.2.29
github_release Patch Available

2.10.2

Patch available: composer/composer 2.10.2

https://github.com/composer/composer/releases/tag/2.10.2
github_commit Patch Available

commit 8887ad76fbd8 (composer/composer)

Patch available: composer/composer 2.10.2 (contains commit 8887ad76fbd8)

https://github.com/composer/composer/commit/8887ad76fbd830cb1861a2b1fd8ead78ed1fa1ec
github_commit Patch Available

commit 6bd66874ae52 (composer/composer)

Patch available: composer/composer 2.2.29 (contains commit 6bd66874ae52)

https://github.com/composer/composer/commit/6bd66874ae523ecb69aca5964487a0cdfda03ef8

Vendor Advisories for CVE-2026-59947(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
composer2.0.11-1 ... 2.9.8-1 (96 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
composer2.10.0-1 ... 2.9.8-1 (56 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
composer2.10.0-1 ... 2.9.8-1 (25 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
composer2.10.0-1 ... 2.9.8-1 (21 versions)2.10.2-1—
Packagist(1)
PackageVulnerable rangeFixed inDependents
composer/composer1.0.0 ... 2.2.9 (149 versions)2.2.29—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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.

  1. 2026-08-27 21:49 UTCEG score recompute
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-26 08:22 UTCEG score recompute
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-24 20:32 UTCEG score recompute
  7. 2026-08-23 19:21 UTCEG score recompute
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 00:19 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 01:58 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 20:48 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-16 22:37 UTCEG score recompute
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:55 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 03:35 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 05:14 UTCEG score recompute
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 06:53 UTCEG score recompute
  25. 2026-08-11 08:32 UTCEG score recompute
Show 49 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-10 10:12 UTCEG score recompute
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-09 11:51 UTCEG score recompute
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-06 16:49 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 20:05 UTCEG score recompute
  10. 2026-08-04 10:39 UTCEPSS rescore
  11. 2026-08-03 21:43 UTCEG score recompute
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 23:23 UTCEG score recompute
  14. 2026-08-02 02:27 UTCEPSS rescore
  15. 2026-08-02 01:02 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-31 04:21 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-29 07:33 UTCEG score recompute
  20. 2026-07-28 15:37 UTCEPSS rescore
  21. 2026-07-28 09:09 UTCEG score recompute
  22. 2026-07-27 14:14 UTCEPSS rescore
  23. 2026-07-27 10:46 UTCEG score recompute
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 12:26 UTCEG score recompute
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-24 14:18 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 14:18 UTCEPSS rescore
  33. 2026-07-23 03:21 UTCEG score recompute
  34. 2026-07-22 14:08 UTCEPSS rescore
  35. 2026-07-22 14:08 UTCEPSS rescore
  36. 2026-07-20 17:08 UTCEPSS rescore
  37. 2026-07-19 14:31 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 17:03 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 02:00 UTCEPSS rescore
  43. 2026-07-15 02:00 UTCEPSS rescore
  44. 2026-07-13 22:31 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-09 19:10 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-08 19:46 UTCEG score recompute
  49. 2026-07-08 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59947?
CVE-2026-59947 is a medium vulnerability published on July 8, 2026. 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…
When was CVE-2026-59947 disclosed?
CVE-2026-59947 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59947 actively exploited?
CVE-2026-59947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.0% of all scored CVEs.
What is the CVSS score of CVE-2026-59947?
CVE-2026-59947 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-59947?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59947, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59947

Explore →

Is Your Infrastructure Affected by CVE-2026-59947?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs