TYPO3-CORE-SA-2026-031: Cache Flooding in Page Cache Handling

It has been discovered that TYPO3 CMS is susceptible to denial of service through page cache flooding.
- Component Type: TYPO3 CMS
- Subcomponent: Cache Handling (ext:frontend)
- Release Date: November 17, 2026
- Vulnerability Type: Cache Flooding
- Affected Versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11
- Severity: High
- Suggested CVSS: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- References: CVE-2026-125162, CWE-770
Problem Description
The cHash argument, which ensures that only URL arguments originally generated by TYPO3 create separate page cache entries, was treated inconsistently when it was passed as an array. The cHash validation treated such a value as missing, while the page cache identifier treated it as present and included all URL arguments. As a result, unauthenticated visitors could create an unlimited number of page cache entries and trigger uncached page renderings by adding an array cHash with arbitrary values to any URL. This could exhaust server resources and fill the page cache storage. Only installations where the cHash validation is not enforced via $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'] are affected. This setting is enabled by default for new installations since TYPO3 v12, but is often still disabled in installations upgraded from older versions.
Solution
Update to TYPO3 versions 10.4.63 ELTS, 11.5.57 ELTS, 12.4.52 ELTS, 13.4.40 LTS or 14.3.12 LTS that fix the problem described.
Additionally, it is recommended to enable $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'].
Credits
Thanks to Christian Huppert for reporting this issue, and to TYPO3 Security Team member Torben Hansen for fixing it.
General Advice
Follow the recommendations that are given in the TYPO3 Security Guide.
General Note
All security-related code changes are tagged so you can easily look them up in our review system.