DRUPAL-CORE-2026-018 in drupal/core
Published 13 Nov 2026 · Updated 18 Nov 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
- <10.6.22 · >=11.0.0 <11.3.22 · >=11.4.0 <11.4.13
- Fixed in
- 10.6.22, 11.3.22, 11.4.13
composer require drupal/core:^11.4.13Details
Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site. This so-called "gadget chain" presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.
This issue 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().
Is DRUPAL-CORE-2026-018 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-132165No summary published · 18 Nov 2026
- 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.