DRUPAL-CORE-2026-017 in drupal/core
Published 18 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 ships with an install.php file for installing Drupal core.
Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution.
Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. In addition to upgrading, the Drupal Security Team recommends securing the Drupal installer after installation.
*Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU.*
Drupal Steward protection:
This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.
Is DRUPAL-CORE-2026-017 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-132166No summary published · 13 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.