CVE-2026-125162 json
TYPO3 CMS - Cache Flooding in Page Cache Handling
published yesterday modified yesterday also EUVD-2026-126979
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- TYPO3 TYPO3 CMS 10.4.63, 11.5.57, 12.4.52, 13.4.40, 14.3.12
- github.com/TYPO3/typo3@7963e23 commit
- github.com/TYPO3/typo3@571bfcd commit
- github.com/TYPO3/typo3@f4f67d1 commit
Is CVE-2026-125162 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | 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 |
| CNA | 4.0 | 8.2 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- TYPO3 TYPO3 CMS
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/TYPO3/typo3/commit/7963e23f3590dbdda037cbf3ee0ee03f61afedce
patch
-
github.com
/TYPO3/typo3/commit/571bfcd1d2a36c70af261d7bdfe5aaa58b295f4b
patch
-
github.com
/TYPO3/typo3/commit/f4f67d18f9c4350ad07876e692aadab1bea16d24
patch
-
news.typo3.com
/security/advisory/typo3-core-sa-2026-031
vendor-advisory
Sources
- CVE List CVE-2026-125162
- NVD CVE-2026-125162
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.