DRUPAL-CORE-2026-017: Composer/drupal/core vulnerability

Published Nov 18, 2026
·
Updated

Update: the Security Team has received a report this was exploited on live sites as early as 2026-11-19 19:00 UTC.

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 (but not all) 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 known attack vectors, but sites should upgrade in the near future in case additional attack vectors are discovered.

Affected Software

3 affected componentsFixes available
composer/drupal/core<10.6.22
10.6.22
composer/drupal/core>=11.0.0<11.3.22
11.3.22
composer/drupal/core>=11.4.0<11.4.13
11.4.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 10.6.22
  2. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 11.3.22
  3. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 11.4.13
  4. Compensating control

    Configure file permissions so the web server cannot write to or change permissions on settings.php.

Event History

Nov 18, 2026
Advisory Published
via OSV·05:43 PM
Data Sourced
via OSV·05:43 PM
DescriptionAffected Software

Frequently Asked Questions

1

What conditions increase the likelihood of a successful takeover or remote code execution attempt?

The issue applies under specific conditions that allow an attacker to use install.php to attempt a Drupal reinstallation. Exploit paths are mitigated when the web server cannot write to or change permissions on settings.php.

2

What should teams do besides upgrading?

Secure the Drupal installer after installation, as recommended by the Drupal Security Team. Restricting the web server's ability to write to or change permissions on settings.php also mitigates some exploit paths.

3

Does Drupal Steward fully mitigate this issue?

No. Drupal Steward protects against some known attack vectors, but it does not cover all possible exploits; affected sites should still upgrade in the near future.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203