DRUPAL-CORE-2025-008 in drupal/core
Published 12 Nov 2025 · Updated 10 Dec 2025
Affected package
- Affected
- >=8.0.0 <10.4.9 · >=10.5.0 <10.5.6 · >=11.0.0 <11.1.9 · >=11.2.0 <11.2.8
- Fixed in
- 10.4.9, 10.5.6, 11.1.9, 11.2.8
composer require drupal/core:^11.2.8Details
The core system module handles downloads of private and temporary files. Contrib modules can define additional kinds of files (schemes) that may also be handled by the system module.
In some cases, files may be served with the HTTP header Cache-Control: public when they should be uncacheable. This can lead to some users getting cached versions of files with information they should not be able to access. For example, files may be cached by Varnish or a CDN.
This vulnerability is mitigated by the following:
1. Drupal must be configured to handle non-public files using a custom or contributed module providing an additional file scheme. 2. An attacker must know to request a file that has previously been requested by a more-privileged user, and that file must still be cached.
Is DRUPAL-CORE-2025-008 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.