Sylius 2.2 · Version Status
Sylius 2.2 End of Life Date
Sylius 2.2 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.
✓
Sylius 2.2 is actively supported. EOL date: March 31, 2027.
📅 Get reminded before Sylius 2.2 reaches EOL on March 31, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Mar 31, 2027
206 days remaining
Latest Release
2.2.9
Standard release
Release Date
Dec 17, 2025
Sylius 2.2 series
Lifecycle detail
Sylius 2.2 was released on December 17, 2025 and support is scheduled to end on March 31, 2027 — a planned supported lifespan of 1 year and 3 months, in line with the 1 year and 4 months median for Sylius releases. It is not an LTS release; Sylius reserves longer patch windows for its LTS versions. Its most recent patch is 2.2.9, published September 2, 2026.
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 →
| Version | Latest | EOL Date | Status |
|---|
| 1.8 |
1.8.12 |
Jan 14, 2022 |
EOL |
| 1.9 |
1.9.13 |
Jul 1, 2022 |
EOL |
| 1.10 |
1.10.17 |
Jan 14, 2023 |
EOL |
| 1.11 |
1.11.18 |
Oct 31, 2023 |
EOL |
| 1.12 |
1.12.25 |
Dec 31, 2024 |
EOL |
| 1.13 |
1.13.17 |
Apr 30, 2025 |
EOL |
| 1.14 LTS |
1.14.20 |
Dec 31, 2026 |
Warning |
| 2.0 |
2.0.18 |
Feb 28, 2026 |
EOL |
What does Sylius 2.2 end of life mean?
When Sylius 2.2 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 Sylius 2.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Sylius 2.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Sylius 2.2 reach end of life?
Sylius 2.2 reached end of life on March 31, 2027. That is 206 days remaining.
Is Sylius 2.2 still supported?
Yes, Sylius 2.2 is currently supported. The EOL date is March 31, 2027.
What should I upgrade to from Sylius 2.2?
The recommended upgrade from Sylius 2.2 is
Sylius 2.2 — the latest actively supported version. Check the
Sylius full timeline for all supported versions.
What are the security risks of running Sylius 2.2 past EOL?
When Sylius 2.2 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 Sylius should migrate immediately or implement compensating controls.