Drupal Core: Request Overrides Can Poison the Page Cache

Published as "Drupal core allows Forceful Browsing"

low Drupal · Last reviewed Nov 8, 2026

CVE: CVE-2025-13080
GHSA: GHSA-83v7-c2cf-p9c2
Packagist: PKSA-bn52-vyzy-rmnm
Reported: Nov 18, 2025

Lets an anonymous attacker make Drupal cache the wrong response, so later visitors get broken or unstyled pages.

Affected and fixed versions

In drupal/core. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
11.2.0 – 11.2.7	11.2.8
11.0.0 – 11.1.8	11.1.9
10.5.0 – 10.5.5	10.5.6

Show 1 older branch

8.0.0 – 10.4.8

10.4.9

Upgrade

Run the line for the branch you are on.

composer require drupal/core:^11.2.8
composer require drupal/core:^11.1.9
composer require drupal/core:^10.5.6

What this means

An attacker without an account can make Drupal cache a response it shouldn't, so later visitors get that cached copy instead of the right page (known as cache poisoning). Drupal's advisory lists the effects as broken rendering, unstyled or badly formatted pages, and client-side features that stop working.

The flaw comes from a rarely used feature in an underlying library that lets some attributes of an incoming HTTP request be overridden. Drupal core has been hardened against it while the library makes its own changes.

Who is affected

Every site on an affected version of drupal/core. Drupal says all module configurations are exploitable, and no login is needed. The advisory doesn't describe any data being exposed or changed beyond what gets cached.

What to do

Update to the fixed release for your branch:

Drupal 10.4: update to 10.4.9
Drupal 10.5: update to 10.5.6
Drupal 11.1: update to 11.1.9
Drupal 11.2: update to 11.2.8

Drupal 11.0.x, 10.3.x and older no longer get security fixes, so move to a supported branch.

Reported by Dragos Dumitrescu, yasser ALLAM, Nils Destoop, Sven Decabooter and zhero.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Drupal Core: Request Overrides Can Poison the Page Cache (CVE-2025-13080, GHSA-83v7-c2cf-p9c2)
Details: https://phpnews.net/security/drupal/ghsa-83v7-c2cf-p9c2

Affected versions, as Composer constraints:
- drupal/core: >=11.2.0,<11.2.8|>=11.0.0,<11.1.9|>=10.5.0,<10.5.6|>=8.0.0,<10.4.9

Fixed releases:
- 11.2.0 – 11.2.7: update to 11.2.8
- 11.0.0 – 11.1.8: update to 11.1.9
- 10.5.0 – 10.5.5: update to 10.5.6

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/drupal/ghsa-83v7-c2cf-p9c2 and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

← All Drupal advisories