Drupal Installer RCE (CVE-2026-132165): What We Know So Far

Drupal Installer RCE (CVE-2026-132165): What We Know So Far

Published: 19 November 2026 | Last Updated: 19 November 2026, UTC

Drupal has released security updates for CVE-2026-132165, a critical vulnerability in its installation functionality that could allow unauthenticated attackers to take over websites or achieve remote code execution (RCE).

Exploitation requires specific conditions, but affected organisations should update promptly and restrict access to the installer. Previdian has not observed exploitation attempts targeting this vulnerability in its honeypot network and is actively monitoring it.

At a Glance

CVECVE-2026-132165
Affected ProductDrupal Core
SeverityCritical (Drupal: 18/25); High (Previdian: CVSS v3.1 8.1)
Exploitation StatusNo confirmed in-the-wild exploitation identified as of 19 November 2026
Public ExploitDrupal lists proof-of-concept maturity; public exploit code not independently verified
Patch AvailableYes
Previdian IntelligenceAdded to Autonomous Watchlist on 19 November 2026; no exploitation observed in honeypot telemetry

What Is CVE-2026-132165?

CVE-2026-132165 is an unauthenticated remote code execution vulnerability affecting Drupal's installation functionality.

Drupal includes an installer at /core/install.php, which may remain accessible after a website has been installed.

Under specific conditions (dropped database connection), an attacker can use this installer to attempt to reinstall an existing Drupal website. Successful exploitation could result in a complete site takeover or remote code execution.

The Drupal Security Team classifies exploitation as complex and the affected configurations as uncommon.

The vulnerability was discovered by Anthropic's OSS Scanner and tracked internally as ANT-2026-GMRPK0BU.

Who Is Affected?

The following Drupal Core versions are affected:

BranchFixed Version
Drupal 10.6.x10.6.22
Drupal 11.3.x11.3.22
Drupal 11.4.x11.4.13

Earlier unsupported branches are also within the advisory's affected ranges. Drupal 10.5.x and earlier, Drupal 11.2.x and earlier, and Drupal 8 and 9 are end-of-life and require migration to a supported release.

Exploitability depends on the deployment configuration, particularly whether the installer is accessible, has dropped database connection, and the web server can modify settings.php or its permissions.

Is CVE-2026-132165 Being Exploited in the Wild?

As of 19 November 2026, Previdian has not observed exploitation attempts targeting CVE-2026-132165 across its honeypot network.

We added the vulnerability to our Autonomous Watchlist on 19 November and are actively monitoring for signs of exploitation.

We have not identified confirmed in-the-wild exploitation in the vendor advisory or the public reporting reviewed.

Drupal's advisory assigns an exploit maturity of Proof, indicating proof-of-concept-level exploitability. This should not be confused with confirmed attacks against production websites.

Previdian have reproduced a partial PoC in our labs.

Is a Patch or Mitigation Available?

Yes. Drupal released fixed versions on 18 November 2026.

Organisations should upgrade to Drupal 10.6.22, 11.3.22 or 11.4.13, depending on their supported branch.

The Drupal Security Team also recommends securing the installer after installation.

Some exploitation paths are mitigated when the web server cannot write to or change permissions on settings.php.

What Should Defenders Do?

  1. Update Drupal Core to the appropriate fixed release and verify the deployed production version.
  2. Block access to /core/install.php after installation, preferably through the web server configuration.
  3. Verify installer restrictions, including /install.php and /core/install.php/foo, which should return HTTP 403 or 404.
  4. Review settings.php permissions to ensure the web server cannot modify the configuration or change its permissions.
  5. Review web server logs for unexpected installer access or reinstallation activity. Requests alone do not establish successful exploitation.

Updates

  • 19 November 2026, UTC: Initial publication. Previdian added the vulnerability to its Autonomous Watchlist. No CVE-matched exploitation attempts have been observed in its honeypot network yet.
  • 18 November 2026, UTC: Drupal published SA-CORE-2026-017 and released security updates.

References

Stay Ahead of Emerging Vulnerabilities

Previdian continuously monitors emerging vulnerabilities and real-world attacker activity, connecting early warning with exposure checks and available temporary defences.

Request a demo to see how Previdian can help your security team identify and respond to emerging threats.