Composer 2.9 · Version Status
Composer 2.9 End of Life Date
Composer 2.9 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Composer 2.9 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
2.9.7
Standard release
Release Date
Nov 13, 2025
Composer 2.9 series
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.10.27 |
Oct 24, 2020 |
EOL |
| 2.0 |
2.0.14 |
Jun 3, 2021 |
EOL |
| 2.1 |
2.1.14 |
Dec 22, 2021 |
EOL |
| 2.2 LTS |
2.2.27 |
EOL |
Active |
| 2.3 |
2.3.10 |
Aug 16, 2022 |
EOL |
| 2.4 |
2.4.4 |
Dec 20, 2022 |
EOL |
| 2.5 |
2.5.8 |
Sep 1, 2023 |
EOL |
| 2.6 |
2.6.6 |
Feb 8, 2024 |
EOL |
What does Composer 2.9 end of life mean?
When Composer 2.9 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Composer 2.9 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Composer 2.9 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Composer 2.9 reach end of life?
Composer 2.9 has already reached end of life.
Is Composer 2.9 still supported?
Yes, Composer 2.9 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Composer 2.9?
The recommended upgrade from Composer 2.9 is
Composer 2.9 — the latest actively supported version. Check the
Composer full timeline for all supported versions.
What are the security risks of running Composer 2.9 past EOL?
When Composer 2.9 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Composer should migrate immediately or implement compensating controls.