Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

Cache Flooding in TYPO3 Frontend

GHSA-pw2q-qwvj-gh43

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 8.3.1, 7.6.11, 6.2.27), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms

    Affected
    >= 6.2.0, < 6.2.27>= 7.6.0, < 7.6.11>= 8.0.0, < 8.3.1
    Fixed in
    6.2.27, 7.6.11, 8.3.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-pw2q-qwvj-gh43

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pw2q-qwvj-gh43

Advisory: Cache Flooding in TYPO3 Frontend
IDs: GHSA-pw2q-qwvj-gh43
Record: https://patchnext.com/advisories/ghsa-pw2q-qwvj-gh43 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 8.3.1, 7.6.11, 6.2.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 6.2.0, < 6.2.27; >= 7.6.0, < 7.6.11; >= 8.0.0, < 8.3.1; fixed in 6.2.27, 7.6.11, 8.3.1

## Suggested inspection (read-only)
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pw2q-qwvj-gh43 (GitHub-reviewed advisory GHSA-pw2q-qwvj-gh43 lists affected ranges: Packagist typo3/cms >=6.2.0 =7.6.0 =8.0.0 <8.3.1)

Commands are suggestions: review each one before running it.

Loading voting…