SYMFONY COVERAGE
Symfony 8.0 and 7.3 are end of life. Your patching does not have to be.
Symfony extended support from OSSeva covers the Symfony versions the Symfony project no longer fixes. Symfony 7.3 reached end of life in January 2026 and Symfony 8.0 in July 2026, and Symfony 8.1 ends in January 2027. Send your work email and an engineer replies within 1 business day with coverage for your Symfony version.
| Who it is for | Teams running Symfony 7.3 or 8.0 who cannot move to a supported line yet because a bundle, a PHP upgrade or a release freeze holds them |
|---|---|
| What you get | Signed patched Symfony components on your line, with your composer.json constraints, bundle configuration and public API unchanged. Assure adds an exposure audit, an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You send your work email, we confirm your Symfony and PHP versions and which components you use, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Symfony support dates, read on 19 November 2026
Symfony releases a minor version every May and November. Standard versions get 8 months of fixes, and the last minor of each major is an LTS release with 3 years of bug fixes and 4 years of security fixes, per the Symfony release process.
| Version | Released | Bug fixes until | Security fixes until | Minimum PHP |
|---|---|---|---|---|
| 7.3 | May 2025 | Jan 2026 (ended) | Jan 2026 (ended) | 8.2.0 |
| 8.0 | Nov 2025 | Jul 2026 (ended) | Jul 2026 (ended) | 8.4.0 |
| 8.1 | May 2026 | Jan 2027 | Jan 2027 | 8.4.0 |
| 6.4 LTS | Nov 2023 | Nov 2026 | Nov 2027 | 8.1.0 |
| 7.4 LTS | Nov 2025 | Nov 2028 | Nov 2029 | 8.2.0 |
Source: symfony.com/releases and the Symfony release process page. endoflife.date lists the same end dates. Symfony 5.4 LTS is also on the releases page, with security fixes until February 2029, which is later than the four-year LTS rule alone would give; we use the date the releases page lists.
Symfony end-of-life dates for every version →symfony.com: releases and support dates →
Symfony and the PHP under it
Symfony 8.0 and 8.1 require PHP 8.4, so those lines run only on PHP that php.net still supports. The older lines are where the PHP risk sits.
- Symfony 6.4 LTS runs on PHP 8.1 or newer. PHP 8.1 ended on 31 December 2025, so a 6.4 site on PHP 8.1 has an unsupported runtime under a supported framework. See [PHP 8.1 end of life](/eol/php-8-1).
- Symfony 7.3 and 7.4 need PHP 8.2 or newer. PHP 8.2 ends on 31 December 2026. See [PHP 8.2 end of life](/eol/php-8-2).
PHP extended support →PHP end-of-life dates →PHP extended support for 7.4 to 8.3 →
Why now
Standard Symfony versions live for eight months
The Symfony release process gives a standard version 8 months of bug and security fixes and an LTS version 3 and 4 years. Symfony 7.3 ended in January 2026 and Symfony 8.0 in July 2026, and Symfony 8.1 follows in January 2027.
Symfony 6.4 LTS bug fixes end in November 2026
symfony.com/releases lists Symfony 6.4 with bug fixes until November 2026 and security fixes until November 2027. After that it is a security-only line, with security fixes to November 2027.
The PHP floor rises with each major
Symfony 8.0 and 8.1 require PHP 8.4, Symfony 7.x requires PHP 8.2 and Symfony 6.4 requires PHP 8.1, per symfony.com/releases. Moving a site forward often means moving PHP first.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 7.3(End of life Jan 2026 (last release 7.3.11)) | EOL | See advisories |
| 8.0(End of life Jul 2026 (last release 8.0.16)) | EOL | See advisories |
| 8.1(Security fixes until Jan 2027. Assessed case by case.) | Current | See advisories |
| 6.4 LTS(Security fixes until Nov 2027. Assessed case by case.) | Current | See advisories |
| 7.4 LTS(Security fixes until Nov 2029. Assessed case by case.) | Current | See advisories |
Running a Symfony version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Symfony 8.0 and 7.3 after end of life.
- Backported security fixes for Symfony 8.0 and 7.3
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Symfony upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which Symfony versions does OSSeva patch?
Symfony 8.0 and 7.3 after end of life. Other versions are assessed case by case through a version coverage check.
How fast are Symfony vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Do I need PHP patched as well as Symfony?
Often yes. Symfony 7.3 needs PHP 8.2 or newer and 8.0 needs PHP 8.4 or newer. The runtime and the framework are patched separately: see PHP extended support for the runtime.
How is OSSeva Symfony support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Symfony patched and supported?
Tell us your Symfony versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?