GHSA-pw2q-qwvj-gh43 — typo3/cms
MEDIUMGHSA-pw2q-qwvj-gh43 is a medium-severity (CVSS 5.3) vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.
Cache Flooding in TYPO3 Frontend
Real-World Exposure
typo3/cms🐘typo3/cms🐘typo3/cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Links with a valid cHash argument lead to newly generated page cache entries. Because the cHash is not bound to a specific page, attackers could use valid cHash arguments for multiple pages, leading to additional useless page cache entries. Depending on the number of pages in the system and the number of available valid links with a cHash, attackers could add a considerable amount of additional cache entries, which in the end exceed storage limits and thus could lead to the system not responding any more. This means the Cache Flooding attack potentially could lead to a successful Denial of Service (DoS) attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms | ≥ 6.2.0&&< 6.2.27 | 6.2.27composer require typo3/cms:^6.2.27 |
| 🐘Packagist | typo3/cms | ≥ 7.6.0&&< 7.6.11 | 7.6.11composer require typo3/cms:^7.6.11 |
| 🐘Packagist | typo3/cms | ≥ 8.0.0&&< 8.3.1 | 8.3.1composer require typo3/cms:^8.3.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 6.2.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw2q-qwvj-gh43 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pw2q-qwvj-gh43 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-pw2q-qwvj-gh43. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pw2q-qwvj-gh43 in your dependencies?
O3 Security finds GHSA-pw2q-qwvj-gh43 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.