Drupal Urges Immediate Upgrade After RCE Bug Lets Hackers Hijack Sites

Drupal has patched a serious security hole in its core installer that could enable remote attackers to seize control of websites without needing an account. The vulnerability, known as CVE-2026-132165, was disclosed on November 18 and stems from the installer component being improperly accessible on sites already in production. That flaw could allow a site reinstallation or even remote code execution.

The installer is meant strictly for creating new Drupal sites. However, when it remains active on a live site under certain conditions, it can be exploited to overwrite existing site data. A successful exploit could expose private data, modify site settings, or even permit full server control. Drupal’s own risk score for this vulnerability sits at 18 out of 25. While it doesn’t require authentication, the attack path is complex and depends on specific server setups.

Who’s affected and how to patch

Sites running Drupal 11.3.x, 11.4.x, or 10.6.x are vulnerable. Users should upgrade to versions 11.3.22, 11.4.13, or 10.6.22 respectively. Earlier branches of 11.x (11.2.x and below), 10.x prior to 10.6.x, and Drupal versions 8 and 9 are no longer supported — upgrade to a secure, active branch if you’re on one of those.

Alongside CVE-2026-132165, recent updates also address CVE-2026-132166, a moderately severe vulnerability involving “gadget chain” risks where existing code could be coerced to run attacker-supplied inputs. While this issue can’t be exploited by itself, in combination with other flaws it adds risk.

While applying the latest Drupal release is the recommended remedy, there are interim mitigations for admins unable to update immediately. Ensuring that the settings.php file is not writable or permissions aren’t changed automatically helps block exploitation paths. Also, some blocking mechanisms by Drupal Steward cover known attack vectors, though they are not full substitutes for the patch. A check via Drupal’s status report can confirm if the vulnerable version is in use.

How this fits into the larger threat landscape

This fix comes not long after two other major Drupal vulnerabilities: a Field UI remote code execution flaw made public in October, and a core SQL injection issue that was flagged by U.S. authorities in May. Neither appears to be tied to the installer exploit or already seen in the wild.

The current issue was reported by Anthropic’s open-source software scanner. Drupal credits it with detecting the flaw and includes proof of concept in its security advisory. Although no real-world attacks have yet been confirmed, admins are being urged not to wait.

Even partial exploits allow attackers to rebuild the application using untrusted input or rerun scripts through writable configuration files. That’s why Drupal has added a safeguard: when settings.php is not writable at install time, the installer will now refuse to tamper with file permissions and instead reveal an error.

Drilling down, the flaw emphasizes the dangers of leaving development or setup tools active on live environments. It also highlights a pattern: Drupal has faced multiple serious issues this year. Administrators need to be vigilant not just about patches, but about their environment’s configuration and what modules, tools, or scripts are exposed.

What to watch for: whether attackers adopt this vulnerability in malware campaigns; whether earlier branches reach exploit maturity; and how quickly site operators move to patch or disable risky installer components. Immediate updating—or at least hardening—is now mission-critical.