Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and from 2.3.0 until 2.10.3, a malicious or compromised dependency can bypass the earlier CVE-2026-59946 binary-path hardening because Composer validates literal parent-directory segments only during dependency resolution, while the symlink and installed-metadata paths described by the advisory skip that validation. A package can ship an in-package binary symlink that resolves outside its installation directory, or attacker-influenced vendor/composer/installed.json metadata can provide an escaping binary path during a reinstall or regeneration of missing vendor/bin entries. The installed-metadata path is reachable only when the vendor directory was not populated by the same validated install run, such as when it is restored from an untrusted cache, copied from an earlier build stage, carried over from an older Composer run, or writable by a lower-trust build step. Composer can follow the path, change the external target's permissions to make it world-readable and executable, and create a runnable vendor/bin proxy to that external file. The issue does not directly read or transmit data and does not by itself provide remote code execution. This issue is fixed in versions 2.2.30 and 2.10.3.
CVE-2026-59944
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% 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).
- 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
- 6.1
- EG Score
- 6.1(medium)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (5)
Auto-updated Sep 16, 20262.2.30
Patch available: composer/composer 2.2.30
https://github.com/composer/composer/releases/tag/2.2.302.10.3
Patch available: composer/composer 2.10.3
https://github.com/composer/composer/releases/tag/2.10.3commit ad649fdfdf8e (composer/composer)
Patch available: composer/composer 2.2.30 (contains commit ad649fdfdf8e)
https://github.com/composer/composer/commit/ad649fdfdf8ed826d4a34e0e5690c76a0b4833aacommit 53b8bb4c2469 (composer/composer)
Patch available: composer/composer 2.10.3 (contains commit 53b8bb4c2469)
https://github.com/composer/composer/commit/53b8bb4c24697b2f00a18cf1ef35a10392701b89Package bin path can escape the package directory, bypassing the GHSA-gjfg-22fp-rrxx fix · Advisory · composer/composer · GitHub
https://github.com/composer/composer/security/advisories/GHSA-96h3-5x6v-m776Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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-09-19 22:37 UTCEG score recompute
- 2026-09-18 21:14 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:49 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 18:24 UTCEG score recompute
- 2026-09-16 17:36 UTCEG score recompute
- 2026-09-16 16:22 UTCEG score recompute
- 2026-09-16 16:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-59
Frequently asked(5)
What is CVE-2026-59944?
When was CVE-2026-59944 disclosed?
Is CVE-2026-59944 actively exploited?
What is the CVSS score of CVE-2026-59944?
How do I remediate CVE-2026-59944?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59944
Is Your Infrastructure Affected by CVE-2026-59944?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.