Zur Hauptnavigation springen Zum Inhalt springen

Category: TYPO3 & security | Reading time: about 8 minutes | Author: Dietmar Engler

Last updated: 17 November 2026, 12:45 CET – the updates have been released. What has changed since the advance notice is listed below under Updates to this article.

Today, 17 November 2026, at around 12:00 CET the TYPO3 Security Team released the announced security updates: TYPO3 14.3.12 and 13.4.40, plus versions 12.4.52, 11.5.57 and 10.4.63 for Extended Long Term Support (ELTS). They fix ten vulnerabilities in the TYPO3 core – one critical, four high and five medium. According to the Security Team, one of them is already being actively exploited.

Install the update today. Then read the section After the update: for some of the vulnerabilities the update alone is not enough, and one change can break forms with file uploads if you overlook it.

Contents

  1. What has been released
  2. The ten vulnerabilities at a glance
  3. What this means for your website
  4. Installing the update
  5. After the update: check these points
  6. If your version is no longer supported
  7. How we handle it for our clients
  8. Updates to this article

What has been released

The advance notice TYPO3-PSA-2026-002 had announced the updates for 12:00 CET today, and they came out on time. Affected and fixed:

  • TYPO3 14 LTS: 14.0.0 to 14.3.11 affected – fixed in 14.3.12.
  • TYPO3 13 LTS: 13.0.0 to 13.4.39 affected – fixed in 13.4.40.
  • TYPO3 12 ELTS: up to 12.4.51 affected – fixed in 12.4.52 (ELTS only).
  • TYPO3 11 ELTS: up to 11.5.56 affected – fixed in 11.5.57 (ELTS only).
  • TYPO3 10 ELTS: up to 10.4.62 affected – fixed in 10.4.63 (ELTS only).

All security advisories are listed at typo3.org/help/security-advisories.

The ten vulnerabilities at a glance

Sorted by severity. The brackets say who can exploit the vulnerability.

  • TYPO3-CORE-SA-2026-027 – critical: installer without authentication. If a file whose name starts with FIRST_INSTALL was placed in the web root or the project root, the installation wizard could be reopened on a website that had long been set up – without logging in. It can be used to create a new administrator account and run arbitrary code. (Anyone who can place such a file – see the next vulnerability.) CVE-2026-119623.
  • TYPO3-CORE-SA-2026-026 – high: online media in the web root. Through “Add online media” (YouTube, Vimeo), any logged-in backend user could create files directly in the public web root, even without file permissions. Combined with SA-2026-027, this is the path to a complete takeover of the website. (Backend users with few permissions.) CVE-2026-119622.
  • TYPO3-CORE-SA-2026-025 – high: path traversal in the Import/Export module. A crafted import file could write arbitrary files to the server, such as a PHP script, and thus run code. (Administrators, or editors for whom importing has been enabled.) CVE-2026-119621.
  • TYPO3-CORE-SA-2026-028 – high: reading files through image processing. With ImageMagick, a file disguised as an image could be processed in a way that puts server files – for example the configuration including credentials – into a publicly accessible image. (Anonymous visitors, if there is an upload without a file type check, such as a public form.) CVE-2026-125159.
  • TYPO3-CORE-SA-2026-031 – high: page cache flooding. Using manipulated URL parameters, visitors could create any number of cache entries and exhaust the server. Installations that do not enforce cHash validation are affected – often websites upgraded from older versions. (Anonymous visitors.) CVE-2026-125162.
  • TYPO3-CORE-SA-2026-029 – medium: form upload folder disclosed – actively exploited. If saving an uploaded file failed, the form showed an error message containing the upload folder that was meant to stay secret. This tells attackers the address of the files they upload. (Anonymous visitors.) CVE-2026-125160.
  • TYPO3-CORE-SA-2026-032 – medium: form uploads without file type restriction. Upload fields without a configured allowed file type accepted almost any file, including HTML and SVG files. Together with SA-2026-029 this enables cross-site scripting. (Anonymous visitors.) CVE-2026-125163.
  • TYPO3-CORE-SA-2026-033 – medium: file delivery with a reusable token. A download token for one file could be reused for other resources with the same ID – including files from non-public storages. (Anonymous visitors.) CVE-2026-125164.
  • TYPO3-CORE-SA-2026-030 – medium: redirects to external sites. An earlier fix (SA-2026-009) was incomplete: crafted links could redirect logged-in backend users to external sites, for example for phishing. (Attackers with a crafted link.) CVE-2026-125161.
  • TYPO3-CORE-SA-2026-034 – medium: server requests through the RSS widget, TYPO3 14 only. The RSS widget in the dashboard could make the server request arbitrary addresses, including internal services. (Backend users with dashboard access.) CVE-2026-125165.

What this means for your website

The advance notice had warned of a critical vulnerability that even backend users with few permissions can exploit. Now it is clear how: any editor account places a file in the web root through the online media function (SA-2026-026), and that file unlocks the installation wizard again (SA-2026-027). From there, a new administrator account is created – and with it full control over the website and the server.

So an editor login is all it takes. And such logins get phished, reused, passed on to interns or external contractors, or never deleted after an employee leaves.

But there is also an attack surface without backend access: if you run public forms with file uploads, you are affected by SA-2026-028, -029 and -032, and one of them is already being exploited.

Installing the update

It is a regular update within your major version, for example from 14.3.11 to 14.3.12 or from 13.4.39 to 13.4.40. In Composer installations this is usually enough:

composer update "typo3/cms-*" --with-dependencies

Without Composer, install the new source package. Then flush the caches, check the database structure in the maintenance area and open the most important pages. Make a backup first.

After the update: check these points

For several of the vulnerabilities, the Security Team names additional steps. The most important ones:

  • Look for traces. Check the web root and the project root for unexpected files whose name starts with FIRST_INSTALL, and review the accounts with administrator or maintainer rights for unknown entries (SA-2026-027).
  • Test upload forms. After the update, an upload field without a configured allowed file type rejects every upload (SA-2026-032). Configure at least one file type for every file and image upload field and test the forms.
  • Protect the upload folder. Files in the forms’ upload folder should be delivered with a strict Content Security Policy. On Apache, the fileadmin/.htaccess shipped with TYPO3 takes care of this; nginx and other web servers have to be configured manually (SA-2026-029).
  • Enforce cHash validation. The Security Team recommends enabling [FE][cacheHash][enforceValidation] if it is not already on (SA-2026-031).
  • TYPO3 14 only: restrict the RSS widget. Here the update does not close the vulnerability on its own. Enter the allowed feed hosts under [HTTP][allowed_hosts][dashboard_rss], or an empty array if nobody uses custom RSS widgets (SA-2026-034).
  • Rare image formats. TYPO3 now only processes formats such as PSD or PPM if they are configured explicitly. If you use them, add them (SA-2026-028).

If your version is no longer supported

The fixes are freely available only for TYPO3 14 and 13. For TYPO3 12, 11 and 10 they are available exclusively through the paid Extended Long Term Support (ELTS); older versions no longer appear in the advisories at all. If your website runs on a version without regular support and without an ELTS contract, the vulnerabilities remain open – including the critical one. Then now is the time to decide on ELTS or an upgrade to a current version. Which versions are maintained for how long is shown on our TYPO3 update service page.

How we handle it for our clients

For the websites in our TYPO3 update service we install the security updates today and take care of the follow-up steps from this article as well – you do not need to do anything.

We rely on t3pilot, our own update manager for all TYPO3 installations we look after. Every night it checks which updates are available and flags security-relevant ones separately. Before every change it creates a complete, encrypted backup; without a successful backup, no update runs. After the update it reloads the most important pages and compares them with the previous state – and if an update does fail, it restores the previous state automatically. That keeps a security update routine, even on a day like today.

Do you look after your TYPO3 website yourself, or are you not sure whether anyone is taking care of it? Get in touch – we can also take over today’s update at short notice.

Updates to this article

  • 17 November 2026, 12:45 CET: The updates have been released. Added version numbers, all ten security advisories and the required follow-up steps.
  • 17 November 2026, 8:30 CET: Advance information based on the announcement TYPO3-PSA-2026-002.
Security update

We install today’s TYPO3 security update for you – with a backup beforehand, the required follow-up steps and a check afterwards. And permanently, if you wish: with our update service your website stays up to date without you having to worry about it.

Frequently asked questions

  • Do I need to act immediately?

    Yes. The updates have been available since midday today, one of the vulnerabilities is critical and another one is already being actively exploited. Install the update today.

  • Which version do I need?

    TYPO3 14.3.12 or 13.4.40. With an ELTS contract: 12.4.52, 11.5.57 or 10.4.63.

  • Is installing the update enough?

    Not in every case. Afterwards, check the web root and the project root for files whose name starts with FIRST_INSTALL, and test forms with file uploads: an upload field without a configured file type no longer accepts files after the update. On TYPO3 14 you also need to define the allowed hosts for the dashboard RSS widget.

  • Only one person has backend access at our company – is the risk low then?

    Lower, but not zero: a backend login with few permissions is enough for the critical vulnerability. If such a login is phished or an old account is still active, it can be exploited. Several vulnerabilities in forms with file uploads can also be exploited without any backend access. The update is therefore necessary in any case.

  • My website runs on an older TYPO3 version. Will I get an update?

    For TYPO3 12, 11 and 10 only with an ELTS contract. For even older versions the advisories list no fixes. Without ELTS the vulnerabilities remain open, and it is time to decide on ELTS or an upgrade.

  • Does this also affect my extensions?

    Today’s ten advisories concern the TYPO3 core. Security advisories for extensions are published separately, also at typo3.org/help/security-advisories.