// PHP extended support

PHP extended support: security patches for 7.4, 8.1, 8.2 and 8.3.
Keep the PHP version you run patched after the PHP project stops.

OSSeva provides PHP security patches for versions 7.4, 8.1, 8.2 and 8.3 after the PHP project stops fixing them. Critical CVEs (CVSS 9.0 or higher) are fixed within 48 hours and High within 7 days. Priced per application runtime, and a senior engineer replies within 1 business day with a quote. PHP 7.4 ended on 28 November 2022 and PHP 8.1 on 31 December 2025, and PHP 8.2 follows on 31 December 2026. Upgrading is usually the better move, and we will tell you so; extended support is for sites held back by a framework release, a vendor certification or a release freeze.

Covered versions
7.4, 8.1, 8.2, 8.3
Critical CVEs
Fixed in 48 hours
High CVEs
Fixed in 7 days
Next end of life
PHP 8.2 · 31 Dec 2026

Dates checked 17 November 2026 against php.net (supported versions and end-of-life pages) and endoflife.date.

PHP 7.4PHP 8.1PHP 8.2PHP 8.3

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Why PHP 7.4 to 8.3 are still in production

Most PHP upgrades are a test run and a framework bump. These are the reasons some sites do not move on the project's schedule.

End of life means new flaws stay open

The PHP project fixes security issues only in supported branches. 7.4 and 8.1 get no fixes now, and 8.2 gets none after 31 December 2026, while releases such as 8.2.34 and 8.2.35 in 2026 fixed flaws that affect the lines behind them.

A framework or a vendor decides the date

An application on an older framework release, or a commercial product certified for one PHP version, cannot always move when the project's calendar says so. The fix window for that site is a decision of the framework or vendor, not of the PHP project.

Every line leaves on a schedule

php.net gives each branch two years of active support and two more of security fixes. 8.3 ends on 31 December 2027 and 8.4 on 31 December 2028, so a team that upgrades to 8.3 now faces the same decision within about a year.

The dates that matter

  1. 2022-11-28

    PHP 7.4 reaches end of life. 7.4.33 is its last release.

  2. 2024-12-31

    Active support for PHP 8.2 ends; it receives security fixes only.

  3. 2025-12-31

    PHP 8.1 reaches end of life. 8.1.34 is its last release.

  4. 2026-12-31

    PHP 8.2 reaches end of life.

  5. 2027-12-31

    PHP 8.3 reaches end of life.

  6. 2028-12-31

    PHP 8.4 reaches end of life.

What OSSeva delivers

1

Patched PHP 7.4, 8.1, 8.2 and 8.3

Security fixes backported to the PHP line you run (8.2 from 31 December 2026 and 8.3 from 31 December 2027), signed. Critical CVEs within 48 hours, High within 7 days. You keep your PHP version.

OSSeva PatchSigned (GPG)48h / 7d
2

Compliance documents and an upgrade plan

A SOC 2 and HIPAA attestation package, 24/7 reactive support and an assessment of the upgrade path to a supported PHP line, so the audit and the move are planned together.

OSSeva AssureAttestationUpgrade plan
3

PHP operated

24/7 application and runtime monitoring, a 15-minute P1 incident response SLA and a named senior engineer on your account.

OSSeva Operate24/715-minute P1

Your options, compared

OptionWhat you getTrade-off
Upgrade to PHP 8.4 or 8.5A line with security support until 31 December 2028 (8.4) or 2029 (8.5)Framework and extension compatibility to test. For most applications this is the right answer.
Upgrade to PHP 8.3The smallest step from 8.2Security support ends 31 December 2027, so another upgrade follows soon.
Third-party PHP supportFixes for ended lines from companies such as HeroDevs, TuxCare and Zend, each with its own version list and termsCompare the versions each one lists and the fix timing it states: they differ.
OSSeva extended supportPatched 7.4, 8.1, 8.2 and 8.3 with a stated patch SLA, on one contract with the rest of your stackA subscription priced per application runtime, for as long as you stay. Other PHP versions are assessed case by case.
Stay unpatchedNothingPHP sites are usually internet-facing, and every new security release adds findings you cannot close.

Dates from php.net/supported-versions.php and php.net/eol.php, cross-checked with endoflife.date on 17 November 2026. Patch SLA and coverage from the OSSeva PHP technology page.

Questions

Frequently asked questions

Book a 15-minute call

Which PHP versions does OSSeva cover?

PHP 7.4, 8.1, 8.2 and 8.3. 8.2 and 8.3 are covered once the PHP project stops fixing them, on 31 December 2026 and 31 December 2027. Other versions are assessed case by case.

How quickly are PHP vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

Are there PHP security patches after end of life?

Not from the PHP project. Third-party providers backport fixes to ended lines, including OSSeva for 7.4, 8.1, 8.2 and 8.3.

When does PHP 8.2 reach end of life?

On 31 December 2026, per php.net. Security-only support has applied since 31 December 2024.

What does PHP extended support cost?

It is priced per application runtime, as the pricing page explains. A senior engineer replies within 1 business day with a quote.

Should we upgrade instead of buying extended support?

Usually, yes. Moving to 8.4 or 8.5 gives years of upstream support. Extended support is for applications that cannot move yet because of a framework release, a vendor certification or a release freeze.

Get a quote

Upgrade what you can.
Patch what you cannot.

Book a discovery call with your PHP versions and frameworks, and we will send a quote priced per application runtime.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call