CVE-2026-125162
The cHash argument, which ensures that only URL arguments originally generated by TYPO3 create separate page cache entries, was treated inconsistently when it …
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of outages.
Affected products · TYPO3
| Product | Affected versions |
|---|---|
| TYPO3 CMS | from 14.0.0 before 14.3.12 from 13.0.0 before 13.4.40 from 12.0.0 before 12.4.52 from 11.0.0 before 11.5.57 from 10.0.0 before 10.4.63 |
Weakness classification
References
- NVD record
- CVE.org record
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-031
- https://github.com/TYPO3/typo3/commit/7963e23f3590dbdda037cbf3ee0ee03f61afedce
- https://github.com/TYPO3/typo3/commit/571bfcd1d2a36c70af261d7bdfe5aaa58b295f4b
- https://github.com/TYPO3/typo3/commit/f4f67d18f9c4350ad07876e692aadab1bea16d24