DRUPAL-CORE-2025-003 in drupal/core
Published 19 Feb 2025 · Updated 19 Sept 2026
Is your project on an affected drupal/core?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=8.0.0 <10.3.13 · >=10.4.0 <10.4.3 · >=11.0.0 <11.0.12 · >=11.1.0 <11.1.3
- Fixed in
- 10.3.13, 10.4.3, 11.0.12, 11.1.3
composer require drupal/core:^11.1.3Details
Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Arbitrary File Inclusion. Techniques exist to escalate this attack to Remote Code Execution. It is not directly exploitable.
This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.
Is DRUPAL-CORE-2025-003 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.
More advisories for drupal/core
- LowCVE-2026-108514No summary published · 14 Oct 2026
- LowCVE-2026-108515No summary published · 14 Oct 2026
- LowCVE-2026-108097No summary published · 14 Oct 2026
- LowDRUPAL-CORE-2026-013No summary published · 16 Sept 2026
- LowCVE-2026-55805No summary published · 15 Jul 2026
- LowCVE-2026-15917No summary published · 15 Jul 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.