CVE
TYPO3 CMS Frontend denial of service via cache flooding in page cache
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
- Exploited
- No known exploitation
- Fix
- Fixed in 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Installations where cHash validation is not enforced via the enforceValidation setting (disabled). TYPO3 CMS 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 or 14.0.0-14.3.11.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
TYPO3 CMS (typo3/cms-frontend) is affected. Remotely and without logging in, an unauthenticated visitor can add an array-style cHash parameter to a URL to create unlimited page cache entries and force uncached page renderings, which can exhaust server resources and fill cache storage. This only applies where cHash validation is not enforced through the enforceValidation setting.
Written by a model from the sources below. Verify against them.
Original 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.
Who should check
Teams running TYPO3 CMS 10.x to 14.3 with cHash enforceValidation disabled, including sites upgraded from older versions.
“Only installations where the cHash validation is not enforced via $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'] are affected.”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Packagist packages
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Installations where cHash validation is not enforced via the enforceValidation setting (disabled). TYPO3 CMS 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 or 14.0.0-14.3.11.Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.
Workaround: Enable $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'].
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125162 (TYPO3 CMS - Cache Flooding in Page Cache Handling), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125162 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-frontend: from 14.0.0, fixed in 14.3.12; from 13.0.0, fixed in 13.4.40; from 12.0.0, fixed in 12.4.52; from 11.0.0, fixed in 11.5.57; from 10.0.0, fixed in 10.4.63
Fixed versions: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.
Conditions (all must be true for the bug to be hit):
- Installations where cHash validation is not enforced via the enforceValidation setting (disabled). (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-031)
- TYPO3 CMS 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 or 14.0.0-14.3.11. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-031)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Enable $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation']. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-031)
CISA KEV: CVE-2026-125162 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125162 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125162
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125162"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- typo3/cms-frontendPackagist
From 14.0.0 · fixed in 14.3.12; From 13.0.0 · fixed in 13.4.40; From 12.0.0 · fixed in 12.4.52; From 11.0.0 · fixed in 11.5.57; From 10.0.0 · fixed in 10.4.63
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Patch
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125162
Is CVE-2026-125162 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets an unauthenticated visitor create unlimited page cache entries and uncached page renderings, which can exhaust server resources and fill page cache storage, causing denial of service.Source: news.typo3.com
Which versions are affected by CVE-2026-125162?
typo3/cms-frontend (Packagist): 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.Source: cve.now feed data
Am I affected, and how do I check?
Only TYPO3 CMS installations where cHash validation is not enforced through the enforceValidation setting in $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash'] are affected. Affected versions are 10.0.0 to 10.4.62, 11.0.0 to 11.5.56, 12.0.0 to 12.4.51, 13.0.0 to 13.4.39, and 14.0.0 to 14.3.11; check the TYPO3 version and that setting in the installation's configuration.Source: news.typo3.com
How do I fix CVE-2026-125162?
Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63. The vendor's advisory also recommends 10.4.63 ELTS or 11.5.57 ELTS or 12.4.52 ELTS or 13.4.40 LTS or 14.3.12 LTS or later.Source: cve.now feed data, news.typo3.com