What Happens After TYPO3 Reaches EOL?

Once TYPO3 reaches End of Life: No security updatesNo bug fixesHigher vulnerability risk An upgrade or ELTS is required to stay secure.

TYPO3 PHP Versions 2026: v14, v13 & v12 Compatibility

Q: Which PHP Version Does TYPO3 13 Need?

TYPO3 v13 needs PHP 8.2 or newer and runs on PHP 8.2 to 8.5. PHP 8.3 or 8.4 is the better choice for production, because PHP 8.2 reaches end of life on 31 December 2026.

Your TYPO3 and PHP versions must fit together. TYPO3 v14 and v13 run on PHP 8.2 to 8.5. TYPO3 v12 runs on PHP 8.1 to 8.4, but its free support ended on 30 April 2026. Since the PHP2Shell security release of 21 October 2026, your PHP patch level matters as well.

Quick answer (checked 28 October 2026):

TYPO3 v14 LTS: PHP 8.2 to 8.5 (recommended for new projects)
TYPO3 v13 LTS: PHP 8.2 to 8.5
TYPO3 v12: PHP 8.1 to 8.4 (free support ended on 30 April 2026, ELTS only)
TYPO3 v11: PHP 7.4 to 8.3 (ELTS only)
Safe PHP patch levels after PHP2Shell: 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and newer

When a PHP version reaches End of Life (EOL), it no longer receives security updates. Newer TYPO3 releases also need modern PHP to run well. An outdated combination leads to extension conflicts, hosting limits and a larger attack surface.

This guide gives you the 2026 compatibility overview, a checker for your PHP version, the lifecycle dates and clear upgrade advice.

ONGOING CONCERN

PHP2Shell: check your PHP patch level now

On 21 October 2026 the PHP team fixed two critical flaws, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. Attacks have been seen since 17 October 2026. A TYPO3 version that supports your PHP branch is not enough: you need PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or newer. PHP 8.1 and older get no official fix. Check your PHP version or read our PHP2Shell guide for TYPO3.

TYPO3 & PHP Compatibility Overview (2026)

Below is the current compatibility status for active and legacy TYPO3 versions.

Currently Supported TYPO3 Versions

TYPO3 v14 LTS
PHP 8.2–8.5
Recommended for new projects
TYPO3 v13 LTS
PHP 8.2–8.5
Proven choice for existing projects

The community supports two LTS versions at any time. For new installations in 2026, TYPO3 v13 or v14 on PHP 8.3 or newer is the preferred baseline.

Extended Support Only (ELTS)

TYPO3 v12: PHP 8.1–8.4. Free community support ended on 30 April 2026.
TYPO3 v11: PHP 7.4–8.3. Free support ended in October 2024.

Both versions only get security fixes through paid ELTS. Use this time to plan the upgrade.

Unsupported TYPO3 Versions (EOL)

The following versions are End of Life:

TYPO3 v10 and older
TYPO3 v9
TYPO3 v8
Any setup running PHP 7.3 or lower

Running EOL software means:

No security patches
Increased attack exposure
Extension incompatibilities
Compliance and hosting risks

These systems need an upgrade plan.

Which TYPO3 Version Should You Run in 2026?

Choose TYPO3 v14 for new projects and the longest support window.
Choose TYPO3 v13 LTS if you want a proven release with security fixes until December 2027.
Move off TYPO3 v12 and v11 as soon as possible. They only get paid ELTS fixes.

Use the latest supported TYPO3 version with PHP 8.3 or newer for security, performance and upgrade flexibility.

Official TYPO3 & PHP Compatibility Matrix

The table shows which PHP versions work with each TYPO3 release. Use it to check whether your setup is supported in 2026.

TYPO3 Version	Supported PHP Versions	Support Status	Recommended for New Projects	Database Requirements
v14 LTS	8.2 – 8.5	LTS, security fixes until June 2029	Yes	MySQL 8.0+ / MariaDB 10.5+ / PostgreSQL
v13 LTS	8.2 – 8.5	LTS, security fixes until December 2027	Yes	MySQL 8.0.17+ / MariaDB 10.4.3+ / PostgreSQL 10+
v12	8.1 – 8.4	Free support ended 30 April 2026, ELTS only	No	MySQL 8.0+ / MariaDB 10.3+
v11	7.4 – 8.3	Extended LTS (paid, security fixes only)	No	MySQL 5.7+ / MariaDB 10.2+
v10	7.2 – 7.4	End of Life (EOL)	No	MySQL 5.5 – 8.0
v9	7.2 – 7.4	End of Life (EOL)	No	MySQL 5.0 – 5.7
v8 and older	7.0 – 7.4 (varies by version)	End of Life (EOL)	No	Legacy MySQL versions

Patch level matters too. Since PHP2Shell, PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are the first safe releases of their branch. PHP 8.1 and older are EOL and have no official fix, whatever TYPO3 version you run.

If your TYPO3 or PHP version is EOL, plan the upgrade without delay. For release dates, see the TYPO3 roadmap and the TYPO3 documentation.

Which PHP version runs with which TYPO3 version

PHP7.4EOLEOL8.0EOLEOL8.1EOLEOL8.2SecuritySec.8.3SecuritySec.8.4ActiveActive8.5ActiveActiveTYPO3 v14 LTSPHP 8.2 – 8.5TYPO3 v13 LTSPHP 8.2 – 8.5TYPO3 v12PHP 8.1 – 8.4 · ELTSTYPO3 v11PHP 7.4 – 8.3 · ELTS

Status as of 28 October 2026. PHP 8.2 security support ends on 31 December 2026 and PHP 8.3 on 31 December 2027. TYPO3 v12 and v11 get fixes only through paid ELTS.

Minimum, Recommended & Future PHP Versions for TYPO3 (2026)

When you plan your TYPO3 environment, two questions matter:

What is the minimum PHP version for TYPO3?
What is the best PHP version for TYPO3 in production?

In 2026, the clear direction is PHP 8.3 and above.

Minimum Required PHP Version

Each TYPO3 version has a defined minimum:

TYPO3 v14 - PHP 8.2
TYPO3 v13 - PHP 8.2
TYPO3 v12 - PHP 8.1
TYPO3 v11 (ELTS) - PHP 7.4

The minimum means the site runs. It does not mean the best performance or long-term security.

Recommended PHP Version for Production

For secure and stable production systems:

TYPO3 v14 and v13 - PHP 8.4 or 8.3
TYPO3 v12 - PHP 8.4 or 8.3, only until you upgrade

PHP 8.2 reaches end of life on 31 December 2026 (see PHP supported versions), so avoid it for new setups. PHP 8.3 gets security fixes until the end of 2027, PHP 8.4 until the end of 2028 and PHP 8.5 until the end of 2029. Always run the latest patch release of your branch.

PHP 8.4 and PHP 8.5 Compatibility

TYPO3 v14 and v13 support PHP 8.4 and PHP 8.5.
TYPO3 v12 supports up to PHP 8.4.

Before you move to a new PHP release:

Confirm TYPO3 core support
Check that your extensions support it
Test in a staging environment

Skipping these checks can cause runtime and dependency errors.

Risks of Running PHP 8.1, 8.0 or 7.4

PHP 8.1 and older no longer get security maintenance, even where an older TYPO3 version still allows them:

No official fix for PHP2Shell
Higher vulnerability exposure
Extension incompatibilities
Hosting upgrade pressure
Compliance concerns

For 2026 production environments, PHP 8.3 or higher is the secure baseline.

PHP2Shell Checker: Is Your PHP Version Safe?

Paste your PHP version, the output of php -v, or an X-Powered-By header. You see at once if you are affected and which TYPO3 versions run on your PHP. Read the full PHP2Shell guide for the five steps to secure a site.

PHP version or output

Runs only in your browser; nothing is sent to us. Find your version in the TYPO3 backend under Admin Tools › Environment › Environment Status, in your hosting panel, or with the command below.

Check from your server (command line)

php -r 'echo PHP_VERSION, " ", PHP_SAPI, PHP_EOL;'

The command-line PHP can differ from the PHP that serves your website. Compare it with the version in TYPO3 Admin Tools.

Other PHP2Shell checkers

OpenAI php2shell-checkerOpen-source tool that reads the PHP version a site reveals or checks your server. Version check only, no exploit. View on GitHub

Pentest-Tools PHP2Shell scannerExternal scan of a website you own. Light scan free; deep scan needs a trial account. Open scanner

External scanners guess the version from headers. Many TYPO3 sites hide it, and Linux distributions often ship the fix without changing the version number. Treat "unknown" as "not confirmed safe".

What Happens If You Run TYPO3 on an Unsupported PHP Version?

Risks of Running TYPO3 on Unsupported PHP

An unsupported PHP version may still run TYPO3, but it raises the risk a lot. Once PHP reaches End of Life (EOL), security updates stop and known flaws stay open. PHP2Shell is a current example: PHP 8.1 and older get no official fix.

Security Vulnerabilities

Without active security patches:

Known exploits stay unpatched
Automated attacks target outdated environments
The risk of data breaches grows

Unsupported PHP widens your attack surface.

GDPR and Compliance Exposure

In regulated environments, outdated infrastructure raises compliance concerns:

Failed security audits
Questioned data protection practices
Higher liability after incidents

Supported software is part of demonstrable risk management.

Hosting Provider Forced Upgrades

Hosting providers routinely drop EOL PHP versions.

This can lead to:

Forced migrations
Service interruptions
Compatibility conflicts after server updates

Planned upgrades prevent reactive downtime.

Extension and Composer Conflicts

Modern TYPO3 extensions and Composer packages target supported PHP releases.

On outdated PHP:

Extensions may stop working
Dependency conflicts increase
Future updates become hard

This builds up technical debt.

Performance and Stability Loss

Older PHP versions lack the speed and memory improvements of newer releases.

The result:

Slower response times
Higher resource usage
Lower stability

Upgrading PHP is often the simplest way to improve TYPO3 performance and reduce risk.

View TYPO3 Performance Guide

In short:

Unsupported PHP may look manageable today, but the security, compliance and operating risks grow over time. Check your PHP version now.

TYPO3 LTS and ELTS Lifecycle Explained

TYPO3 follows a clear and predictable release lifecycle. Knowing LTS and ELTS helps you plan and control risk.

How Long Does TYPO3 LTS Last?

Each Long Term Support (LTS) release provides:

About 3 years of community support
Regular bug fixes and security updates
A stable base for enterprise sites

The community supports two LTS versions at any time. Current dates, according to TYPO3 News:

TYPO3 v14: bug fixes until December 2027, security fixes until June 2029
TYPO3 v13: security fixes until December 2027
TYPO3 v12: free support ended on 30 April 2026

What ELTS Includes (and What It Does Not)

After the LTS phase ends, Extended Long Term Support (ELTS) is available as a paid program from TYPO3 GmbH. For TYPO3 v12 it covers up to three more years, with a fourth year for TYPO3 partners.

ELTS includes:

Security fixes
Critical patches
A longer support window

ELTS does not include:

New features
Functional improvements
Major compatibility upgrades

ELTS keeps security coverage in place, but it does not modernize the system.

When ELTS Makes Strategic Sense

ELTS can fit when:

An immediate upgrade is not possible
Internal resources are tight for now
A structured migration plan is already running

In this case, ELTS is a controlled transition period.

When You Should Upgrade Instead

Upgrading is the better option when:

You skipped several TYPO3 versions
You need modern extensions
You want better performance
Long-term digital strategy is a priority

ELTS is a temporary safeguard. For business-critical systems, upgrading to a supported TYPO3 version is the more sustainable path.

Recommended Upgrade Paths in 2026

If your TYPO3 version is outdated, upgrading is risk management, not housekeeping. Here is what to do for your current setup.

If You Are on TYPO3 v9 or v10

These versions are End of Life (EOL)
Upgrade to TYPO3 v14 (preferred) or v13 LTS
Do not keep them in production

If You Are on TYPO3 v11

Only ELTS (security fixes only) is available
Plan the upgrade to v14 or v13 now
Use ELTS only as a temporary bridge

If You Are on TYPO3 v12

Free support ended on 30 April 2026
Upgrade to v13 or v14, or buy ELTS while you prepare
Update PHP to a patched 8.3 or 8.4 release at once

If You Are on TYPO3 v13

Fully supported, safe to run
Use PHP 8.3 or 8.4 on the latest patch level
Plan the move to v14 before December 2027

Planning a Multi-Version Upgrade

If you are several versions behind:

Audit your extensions
Test in staging
Plan phased upgrades if needed

Structured upgrades reduce risk and downtime. Our TYPO3 team can help: request a free check.

How to Check the PHP Version of Your TYPO3 Website

Before you upgrade, confirm your current PHP version, including the patch number such as 8.3.36.

Not sure which TYPO3 version you run? Read how to check your TYPO3 version.

Check via TYPO3 Backend

Check the PHP Version of Your TYPO3 Website via Backend

Log in to TYPO3
Open Admin Tools › Environment › Environment Status, or the System Information item in the toolbar
Read the listed PHP version

Check via Command Line

Run php -v on the server. The command-line PHP can differ from the PHP your web server uses, so compare it with the backend value.

Check via phpinfo File

Create a file named phpinfo.php with:

<?php phpinfo(); ?>

Open it in your browser to see the PHP version.

Security Best Practice After Checking

Delete the phpinfo.php file immediately
Do not leave diagnostic files on the server

Knowing your TYPO3 and PHP versions is the first step to a safe setup. Then use the PHP2Shell checker above to see if your patch level is safe.

Server & Environment Requirements Beyond PHP

PHP compatibility alone is not enough. A stable TYPO3 installation also depends on correct server settings, database versions and matching components. The table shows the key requirements for 2026.

Requirement Area	Minimum Requirement	Recommended for Production (2026)	Why It Matters
PHP Version	8.2 (v14, v13), 8.1 (v12)	PHP 8.3 or 8.4 on the latest patch level	Security fixes and extension support
PHP Patch Level	Any release of a supported branch	8.5.12, 8.4.27, 8.3.36 or 8.2.35 and newer	Closes the PHP2Shell flaws
PHP Extensions	pdo_mysql, mbstring, intl, json, openssl, tokenizer, xml	All required extensions enabled + OPcache active	Missing extensions cause installation or runtime failures
Database (MySQL)	MySQL 8.0.17+ (v13), 8.0+ (v14)	MySQL 8.0 or newer, latest stable	Performance, security updates and compatibility
Database (MariaDB)	MariaDB 10.3+ (v12), 10.4.3+ (v13), 10.5+ (v14)	Latest stable MariaDB release	Stable DBAL and schema handling
Composer Version	Composer 2.x	Latest Composer 2 release	Dependency management for modern TYPO3 setups
CLI vs Web PHP	Must match major version	Same PHP version for CLI and web server	Prevents upgrade and rollout conflicts
Memory Limit	256MB	512MB or higher (enterprise: 768MB+)	Prevents upgrade failures and backend crashes
PHP OPcache	Optional	Enabled and configured	Faster response times

Even if your TYPO3 and PHP versions fit, a mismatched server setup can cause:

Upgrade failures
Extension conflicts
Rollout issues
Unstable performance

A clean environment reduces technical debt and makes upgrades smoother.

Why Upgrading TYPO3 Is a Strategic Decision (Not Just Technical)

Upgrading TYPO3 affects security, compliance, performance and long-term planning. It is a strategic decision, not only a technical update.

Security and Long-Term Risk Management

Outdated TYPO3 and PHP versions increase exposure to:

Known vulnerabilities such as PHP2Shell
Unsupported dependencies
Audit and compliance risks

Regular upgrades reduce operational risk and support responsible IT governance. Security is a core operating requirement.

Performance Gains with PHP 8.x

Modern PHP versions (8.3+) deliver:

Faster execution
Better memory efficiency
Better overall stability

Combined with newer TYPO3 improvements, this means faster backend work and a quicker frontend.

Extension Ecosystem Compatibility

TYPO3 extensions keep evolving. New releases target supported TYPO3 and PHP versions.

Staying current gives you:

Access to new features
Ongoing vendor support
Fewer integration conflicts

Delaying upgrades increases technical debt.

A Stable Base for the Next Years

Running current TYPO3 and PHP versions:

Simplifies later upgrades
Reduces migration effort
Keeps you inside the support window

For enterprise and regulated environments, predictable lifecycle management is essential. Upgrading TYPO3 is an investment in stability, security and reliable TYPO3 support & maintenance.

Request a Free PHP and TYPO3 Check

Tell us your website, PHP version and TYPO3 version, and choose a service. Our TYPO3 team replies within one business day.

Conclusion

TYPO3 and PHP compatibility is not a one-time decision. It needs lifecycle awareness, planning and timely upgrades. Supported versions give you security coverage, stable extensions and easier maintenance.

In 2026 and beyond, TYPO3 v13 or v14 on PHP 8.3 or newer, at the latest patch level, is the most reliable base. Once your technical base is current, the AI Foundation for TYPO3 gives you a structured way to add and govern AI features.

If your site runs on an outdated TYPO3 or an unsupported PHP version, a structured TYPO3 Upgrade is a necessary step. Not sure where you stand? Check your PHP version or request a free check.

FAQs

TYPO3 v13 needs PHP 8.2 or newer and runs on PHP 8.2 to 8.5. PHP 8.3 or 8.4 is the better choice for production, because PHP 8.2 reaches end of life on 31 December 2026.

No. PHP 8.0 reached end of life in 2023 and PHP 8.1 at the end of 2025. Use PHP 8.3 or newer. Only TYPO3 v12 and v11 (ELTS) still run on PHP 8.1.

Only TYPO3 v11 (under ELTS) supports PHP 7.4. Newer TYPO3 versions need PHP 8.1 or higher. PHP 7.4 is end of life and has no official PHP2Shell fix.

Yes. TYPO3 v14 and v13 support PHP 8.2 to 8.5. TYPO3 v12 supports up to PHP 8.4. Check your extensions and test in staging before you switch.

Once TYPO3 reaches End of Life:

No security updates
No bug fixes
Higher vulnerability risk

An upgrade or ELTS is required to stay secure.

ELTS is useful as a short-term solution when an immediate upgrade is not possible. It provides security fixes but no new features or improvements.

TYPO3 v13 gets security fixes until the end of December 2027. After that, paid ELTS is available.

For long-term planning, follow the official TYPO3 roadmap.

Free community support for TYPO3 v12 ended on 30 April 2026. Security fixes now come only through paid ELTS. Plan the upgrade to TYPO3 v13 or v14.

PHP2Shell is the name for two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026. TYPO3 runs on PHP, so every TYPO3 site on an unpatched PHP version is exposed. The TYPO3 version itself does not matter, the PHP patch level does.

Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or any newer release of your branch. PHP 8.1 and older get no official fix. Use the checker on this page to test your version.

Sources and Further Reading

We checked the dates and version ranges in this guide on 28 October 2026 against these sources. We update the guide when TYPO3 or PHP change their support dates.

Wolfgang Weber

Brand & Communication Lead

Wolfgang Weber shapes TYPO3 with passion and expertise. As a TYPO3 enthusiast at T3Planet Shop, he has contributed to TYPO3 projects that make websites faster and more secure. Outside of TYPO3, you’ll probably find him exploring local cafés and enjoying football.