Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-125162

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

Overview

Published
17 Nov 2026
Modified
17 Nov 2026
High CVE
1 Registry packages
0 OS packages
0 Linux distributions
No Fix available
CVSS score High, no score

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.

Source: OX vulnerability database

Severity

HIGH

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-770

Affected packages · 1

Packages affected by CVE-2026-125162
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms-frontend >=14.0.0, <14.3.12>=13.0.0, <13.4.40>=12.0.0, <12.4.52>=11.0.0, <11.5.57>=10.0.0, <10.4.63 No fix yet

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.