
November 17, 2026 4 min read
Patch day without the pulse spike: the TYPO3 14.3.12 security update
TYPO3 14.3.12 and 13.4.40 LTS as well as several ELTS versions were released today with ten security fixes. A thank-you to the TYPO3 Security Team and a short look at why such an update does not have to be a drama if you are prepared.
Ten vulnerabilities, one release day
Today, on 17 November 2026, the TYPO3 project released TYPO3 14.3.12 LTS and 13.4.40 LTS, along with the ELTS versions 12.4.52, 11.5.57 and 10.4.63. Together they fix ten security vulnerabilities (TYPO3-CORE-SA-2026-025 to -034). The range goes from information disclosure in the Form Framework and the File Dump Controller, through an open redirect and path traversal in the import/export module, to an unrestricted file upload.
The one that stands out is TYPO3-CORE-SA-2026-027, rated critical: a marker file with the prefix FIRST_INSTALL could re-enable the installer on an instance that had long been set up, without any authentication. Anyone who gets there can redirect the database connection and create an admin account for themselves. From there, remote code execution is not far off. The combination with SA-2026-026 makes it particularly nasty: according to that advisory, even a restricted backend user could create such a file. All versions from 10.0.0 up to and including 14.3.11 are affected.
All the details are in the official announcement and the security advisories.
Thank you, TYPO3 Security Team!
Before we get to the technical side: ten advisories on a single day, neatly coordinated across five version branches from v10 to v14, each with a clear description, affected versions, severity and concrete recommendations. This shows that the Security Team is doing a really great job!
Behind every advisory there is a whole chain: someone reports a vulnerability responsibly, the Security Team assesses it, develops a fix, tests it across all supported versions, writes the advisories and coordinates the release date. And all of that without anything leaking beforehand. My heartfelt thanks go to the TYPO3 Security Team and to everyone who reported the vulnerabilities. You make TYPO3 a system that can be trusted with a clear conscience, even in enterprise use.
When you know something is coming
The best part of a security update is the part that happens beforehand. The Security Team usually announces releases containing security fixes in advance, via the typo3-announce mailing list and on typo3.org. There are no details at that point, but you do get the date and the affected versions. If you are subscribed, you can plan for release day instead of being surprised by it.
That is why a patch day is pretty unspectacular for me:
- Create a branch from the current stage state.
composer updatein the DDEV container. For a patch release within 14.3, this is usually just a matter of swapping packages. According to the announcement, no database upgrades are needed this time.- Check Composer patches: if a local patch has since landed in the core or no longer applies, it gets removed or adjusted.
- Run the linters, commit, push, merge request.
From there, the pipeline takes over. GitLab CI builds the frontend and TYPO3, runs PHP-CS-Fixer, PHPStan, Rector, Fractor and the frontend linters, and deploys to stage. Then Playwright tests in several browsers check that the site still does what it should. If everything is green, the same state goes live via merge request. By the way, I have already described how this build chain is set up in Buildchain with GitLab CI for your TYPO3 project.
The crucial point: there is no manual step on the server. Nobody logs in via SSH, nobody uploads files, nobody forgets the cache. The update is a perfectly normal commit, with history and tests, and traceable at any time.
Don't forget: two configuration steps
This time, an update alone is not quite enough. Two advisories additionally recommend some configuration:
- SA-2026-034 (SSRF in the dashboard RSS widget, v14 only): Add the allowed hosts for RSS feeds to
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['allowed_hosts']['dashboard_rss']. If you don't use any custom RSS widgets, set an empty array here. Without this setting, the vulnerability stays open despite the update. - SA-2026-031 (cache flooding): Only affects installations without enforced cHash validation. On new installations,
$GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation']has been active since v12, but on older projects that were upgraded over time it often is not. Make sure to check.
In connection with SA-2026-027, the Security Team also recommends checking the web root and the project directory for files whose names start with FIRST_INSTALL, and going through the list of admin and system maintainer accounts for any unknown entries.
Conclusion
Security updates are no reason to panic, as long as two things are in place: you know in good time that something is coming, and the path from composer update to the live server is automated and tested. The TYPO3 Security Team takes care of the first part brilliantly. The second you have to build once, but it pays off on every patch day.
So: subscribe to the mailing list, automate your deployment and update today. If you are not on 14.3.12 or 13.4.40 yet, now is a good time. :)



Comments (0)
No comments found!