Symfony EOL: end-of-life dates for every Symfony version
Symfony 8.0 reached end of life in July 2026 and Symfony 7.3 in January 2026. Symfony 8.1 ends in January 2027, Symfony 6.4 LTS gets security fixes until November 2027 and Symfony 7.4 LTS until November 2029. OSSeva patches Symfony 8.0 and 7.3 after end of life. Dates checked against symfony.com and endoflife.date on 19 November 2026.
- Latest release
- 8.1.11
- Supported lines
- 4
- End-of-life lines
- 26
- Next end of life
- 8.1 · 31 Jan 2027
Symfony 8.0 and 7.3 have ended
Upgrade to 7.4 LTS or 8.1, or keep 8.0 and 7.3 patched
A standard Symfony version lives eight months, so most teams move one minor at a time. When a bundle, a PHP upgrade or a release freeze holds a site on an ended line, OSSeva patches Symfony 8.0 and 7.3 after end of life. Other versions are assessed case by case through a version coverage check. Critical fixes ship within 48 hours and High within 7 days.
Who patches Symfony after end of life
OSSeva provides Symfony extended support: patched, signed builds for Symfony 8.0 and 7.3 after upstream support ends, plus 24/7 operations on the Operate tier.
Symfony release timeline
All Symfony versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 8.1 | 6 months ago(29 May 2026) | Ends in 2 months(31 Jan 2027) | Ends in 2 months(31 Jan 2027) | 8.1.11 | – |
| 8.0 | 1 year ago(27 Nov 2025) | Ended 4 months ago(31 Jul 2026) | Ended 4 months ago(31 Jul 2026) | 8.0.16 | Patched |
| 7.4 (LTS) | 1 year ago(27 Nov 2025) | Ends in 2 years(30 Nov 2028) | Ends in 3 years(30 Nov 2029) | 7.4.23 | – |
| 7.3 | 1 year and 6 months ago(29 May 2025) | Ended 10 months ago(31 Jan 2026) | Ended 10 months ago(31 Jan 2026) | 7.3.11 | Patched |
| 7.2 | 2 years ago(29 Nov 2024) | Ended 1 year and 4 months ago(31 Jul 2025) | Ended 1 year and 4 months ago(31 Jul 2025) | 7.2.9 | – |
| 7.1 | 2 years and 6 months ago(31 May 2024) | Ended 1 year and 10 months ago(31 Jan 2025) | Ended 1 year and 10 months ago(31 Jan 2025) | 7.1.11 | – |
| 7.0 | 3 years ago(29 Nov 2023) | Ended 2 years and 4 months ago(31 Jul 2024) | Ended 2 years and 4 months ago(31 Jul 2024) | 7.0.10 | – |
| 6.4 (LTS) | 3 years ago(29 Nov 2023) | Ends in 8 days(30 Nov 2026) | Ends in 1 year(30 Nov 2027) | 6.4.50 | – |
| 6.3 | 3 years and 6 months ago(30 May 2023) | Ended 2 years and 10 months ago(31 Jan 2024) | Ended 2 years and 10 months ago(31 Jan 2024) | 6.3.12 | – |
| 6.2 | 4 years ago(30 Nov 2022) | Ended 3 years and 4 months ago(31 Jul 2023) | Ended 3 years and 4 months ago(31 Jul 2023) | 6.2.14 | – |
| 6.1 | 4 years and 6 months ago(27 May 2022) | Ended 3 years and 10 months ago(31 Jan 2023) | Ended 3 years and 10 months ago(31 Jan 2023) | 6.1.12 | – |
| 6.0 | 5 years ago(29 Nov 2021) | Ended 3 years and 10 months ago(31 Jan 2023) | Ended 3 years and 10 months ago(31 Jan 2023) | 6.0.20 | – |
| 5.4 (LTS) | 5 years ago(29 Nov 2021) | Ended 2 years ago(30 Nov 2024) | Ends in 2 years and 3 months(28 Feb 2029) | 5.4.56 | – |
| 5.3 | 5 years and 6 months ago(31 May 2021) | Ended 4 years and 11 months ago(1 Jan 2022) | Ended 4 years and 11 months ago(1 Jan 2022) | 5.3.16 | – |
| 5.2 | 6 years ago(30 Nov 2020) | Ended 5 years and 4 months ago(21 Jul 2021) | Ended 5 years and 4 months ago(21 Jul 2021) | 5.2.14 | – |
| 5.1 | 6 years and 6 months ago(31 May 2020) | Ended 5 years and 10 months ago(21 Jan 2021) | Ended 5 years and 10 months ago(21 Jan 2021) | 5.1.11 | – |
| 5.0 | 7 years ago(21 Nov 2019) | Ended 6 years and 4 months ago(21 Jul 2020) | Ended 6 years and 4 months ago(21 Jul 2020) | 5.0.11 | – |
| 4.4 (LTS) | 7 years ago(21 Nov 2019) | Ended 4 years ago(21 Nov 2022) | Ended 3 years ago(21 Nov 2023) | 4.4.51 | – |
| 4.3 | 7 years and 6 months ago(30 May 2019) | Ended 6 years and 11 months ago(1 Jan 2020) | Ended 6 years and 5 months ago(1 Jul 2020) | 4.3.11 | – |
| 4.2 | 8 years ago(30 Nov 2018) | Ended 7 years and 5 months ago(1 Jul 2019) | Ended 6 years and 11 months ago(1 Jan 2020) | 4.2.12 | – |
| 4.1 | 8 years and 6 months ago(30 May 2018) | Ended 7 years and 11 months ago(1 Jan 2019) | Ended 7 years and 5 months ago(1 Jul 2019) | 4.1.13 | – |
| 4.0 | 9 years ago(30 Nov 2017) | Ended 8 years and 5 months ago(1 Jul 2018) | Ended 7 years and 11 months ago(1 Jan 2019) | 4.0.15 | – |
| 3.4 (LTS) | 9 years ago(30 Nov 2017) | Ended 6 years and 1 month ago(1 Nov 2020) | Ended 5 years and 1 month ago(1 Nov 2021) | 3.4.49 | – |
| 3.3 | 9 years and 6 months ago(29 May 2017) | Ended 8 years and 11 months ago(1 Jan 2018) | Ended 8 years and 5 months ago(1 Jul 2018) | 3.3.18 | – |
| 3.2 | 10 years ago(30 Nov 2016) | Ended 9 years and 5 months ago(1 Jul 2017) | Ended 8 years and 11 months ago(1 Jan 2018) | 3.2.14 | – |
| 3.1 | 10 years and 6 months ago(30 May 2016) | Ended 9 years and 11 months ago(1 Jan 2017) | Ended 9 years and 5 months ago(1 Jul 2017) | 3.1.10 | – |
| 3.0 | 11 years ago(30 Nov 2015) | Ended 10 years and 5 months ago(1 Jul 2016) | Ended 9 years and 11 months ago(1 Jan 2017) | 3.0.9 | – |
| 2.8 (LTS) | 11 years ago(30 Nov 2015) | Ended 8 years and 1 month ago(1 Nov 2018) | Ended 7 years and 1 month ago(1 Nov 2019) | 2.8.52 | – |
| 2.7 (LTS) | 11 years and 6 months ago(30 May 2015) | Ended 8 years and 7 months ago(1 May 2018) | Ended 7 years and 7 months ago(1 May 2019) | 2.7.52 | – |
| 2.3 (LTS) | 13 years and 6 months ago(3 Jun 2013) | Ended 10 years and 7 months ago(1 May 2016) | Ended 9 years and 7 months ago(1 May 2017) | 2.3.42 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: symfony.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Symfony 5.4, 6.4, 7.4, 8.0 and 8.1 support dates
Symfony ships a minor version every May and November and a major every two years. A standard version gets eight months of fixes. The last minor of each major is an LTS release with three years of bug fixes and four years of security fixes, so 6.4 and 7.4 are the lines that last.
Symfony support dates. Sources: symfony.com/releases and endoflife.date, read on 19 November 2026.
| Version | Released | Bug fixes until | Security fixes until | Minimum PHP | Latest release |
|---|---|---|---|---|---|
| 7.3 | May 2025 | Jan 2026 | Jan 2026 (ended) | 8.2.0 | 7.3.11, 28 Jan 2026 |
| 8.0 | Nov 2025 | Jul 2026 | Jul 2026 (ended) | 8.4.0 | 8.0.16, 29 Jul 2026 |
| 8.1 | May 2026 | Jan 2027 | Jan 2027 | 8.4.0 | 8.1.11, 4 Nov 2026 |
| 5.4 LTS | Nov 2021 | Nov 2024 | Feb 2029 | 7.2.5 | 5.4.56, 4 Nov 2026 |
| 6.4 LTS | Nov 2023 | Nov 2026 | Nov 2027 | 8.1.0 | 6.4.50, 4 Nov 2026 |
| 7.4 LTS | Nov 2025 | Nov 2028 | Nov 2029 | 8.2.0 | 7.4.23, 4 Nov 2026 |
The 5.4 security date follows symfony.com/releases and endoflife.date, which both give February 2029. That is later than the four-year LTS rule on the release process page alone would give (November 2025), so check your 5.4 plan against the releases page. Symfony 8.2 is listed as a November 2026 release but was a beta (8.2.0-BETA2) on the read date.
Upgrading Symfony: minors, majors and the PHP floor
Symfony's backward compatibility promise decides how hard each move is. A minor upgrade (7.3 to 7.4, 8.0 to 8.1) contains no backward-incompatible changes: old APIs keep working and are marked deprecated. A major upgrade removes what was deprecated, so the project's documented route is to reach the last minor of your major, clear every deprecation notice, then change the symfony/* constraints to the next major.
That makes the PHP floor, not the framework code, the usual blocker. Symfony 8.0 and 8.1 require PHP 8.4, so staying on 8.1 means a PHP 8.4 runtime. Symfony 7.x needs PHP 8.2 and 6.4 needs PHP 8.1, which ended on 31 December 2025. A 5.4 site, which needs only PHP 7.2.5, has the widest gap to close: 5.4 to 6.4 is a major upgrade that also moves PHP to 8.1 at least.
Upgrade routes by starting version. Sources: symfony.com/releases and the Symfony upgrade documentation, read on 19 November 2026.
| From | To | Kind of change | PHP needed at the target |
|---|---|---|---|
| 7.3 | 7.4 LTS | Minor: no backward-incompatible changes | 8.2.0, same as 7.3 |
| 8.0 | 8.1 | Minor: no backward-incompatible changes | 8.4.0, same as 8.0 |
| 6.4 LTS | 7.4 LTS | Major: fix 6.4 deprecations first, then change constraints | 8.2.0, up from 8.1.0 |
| 5.4 LTS | 6.4 LTS | Major: fix 5.4 deprecations first, then change constraints | 8.1.0, up from 7.2.5 |
After changing constraints the upgrade guide also tells you to update Flex recipes with composer recipes:update and read the UPGRADE file for the new major. Where a third-party bundle has not published a release for the target line, the deprecation route stops at that bundle.
Who patches Symfony after end of life?
The Symfony project ships no fixes for a line after its end date. HeroDevs' own support page, read on 19 November 2026, does not list Symfony among its products and says coverage expands based on customer demand. OSSeva patches Symfony 8.0 and 7.3 after end of life.
Facts from each provider's own page, read on 19 November 2026.
| Provider | Symfony versions the page lists | Fix timing the page states |
|---|---|---|
| HeroDevs | None: Symfony is not on its support page | Not applicable |
| OSSeva | 8.0 and 7.3. Other versions case by case | Critical within 48 hours, High within 7 days |
How we compared: HeroDevs' row uses only its own support page. We did not read other providers' pages and have not listed them, so this table does not show that nobody else sells Symfony fixes.
Running an end-of-life Symfony version?
OSSeva keeps end-of-life Symfony patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Symfony extended supportIs Symfony 5.4 end of life?
Not yet on the dates symfony.com/releases lists. Symfony 5.4 LTS had bug fixes until November 2024 and has security fixes until February 2029. It needs only PHP 7.2.5, so check the PHP version under it.
When does Symfony 6.4 LTS reach end of life?
Symfony 6.4 LTS has bug fixes until November 2026 and security fixes until November 2027. It requires PHP 8.1 or newer, and PHP 8.1 ended on 31 December 2025.
Is Symfony 7 end of life?
Partly. Symfony 7.0 to 7.3 have ended, with 7.3 ending in January 2026. Symfony 7.4 is an LTS release with bug fixes until November 2028 and security fixes until November 2029.
Is Symfony 8.0 end of life?
Yes. Symfony 8.0 ended in July 2026 and 8.0.16 was its last release, on 29 July 2026. Symfony 8.1 is supported until January 2027. OSSeva patches Symfony 8.0 after end of life.
What is the Symfony LTS version?
Symfony 7.4 is the current LTS release, with security fixes until November 2029. Symfony 6.4 is also an LTS line. The last minor of each major is the LTS, so 8.4 is the next one.
Who provides Symfony support after end of life?
OSSeva patches Symfony 8.0 and 7.3 after end of life and assesses other versions case by case through a version coverage check. HeroDevs' support page does not list Symfony, read on 19 November 2026.
What is the latest Symfony version?
8.1.11, released 4 Nov 2026, on the 8.1 line. Other supported lines: 7.4, 6.4 and 5.4.
When is the next Symfony end of life?
Symfony 8.1 reaches the end of security support on 31 Jan 2027. After that date the project stops shipping security fixes for 8.1, and CVEs disclosed later stay unpatched upstream.
Which Symfony versions are still supported?
8.1 (until 31 Jan 2027), 7.4 (until 30 Nov 2029), 6.4 (until 30 Nov 2027) and 5.4 (until 28 Feb 2029). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Symfony version?
Yes. OSSeva ships signed builds with backported CVE fixes for Symfony 8.0 and 7.3 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Get a quote
Still running an end-of-life Symfony?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?