Composer 1 · Version Status
Composer 1 End of Life Date
Composer 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Composer 1 is past end of life. This version no longer receives security patches. 161 days past EOL — migrate to a supported version immediately.
EOL Date
May 30, 2026
161 days past EOL
Latest Release
1.10.28
Standard release
Release Date
Apr 5, 2016
Composer 1 series
Where these dates come from
End of lifeMay 30, 2026Vendor's own page, checked by a person · getcomposer.org · checked Nov 1, 2026high · 2 sources agree ReleaseApr 5, 2016Vendor's own page, checked by a person · getcomposer.org · checked Nov 1, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Composer 1 was released on April 5, 2016 and support ended on May 30, 2026 — a supported lifespan of 10 years and 2 months, longer than the 7 months median for Composer releases. It was not an LTS release; Composer reserves longer patch windows for its LTS releases. Its latest release on record is 1.10.28, published May 13, 2026 — 17 days before support ended. It has been past its end-of-life date for 5 months. 1 newer Composer release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Composer 1 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.10.28 |
May 30, 2026 |
EOL |
| 2.0 |
2.0.14 |
Jun 3, 2021 |
EOL |
| 2.1 |
2.1.14 |
Dec 22, 2021 |
EOL |
| 2.2 LTS |
2.2.31 |
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 1 end of life mean?
When Composer 1 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Composer 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Composer 2.11 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Composer 1 reach end of life?
Composer 1 reached end of life on May 30, 2026. This version is no longer receiving security patches.
Is Composer 1 still supported?
No. Composer 1 reached end of life on May 30, 2026 and is no longer receiving security patches.
What should I upgrade to from Composer 1?
The recommended upgrade from Composer 1 is
Composer 2.11 — the latest actively supported version. Check the
Composer full timeline for all supported versions.
What are the security risks of running Composer 1 past EOL?
Since Composer 1 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Composer should migrate immediately or implement compensating controls.