Drupal Fixes Critical RCE Flaw That Could Let Unauthenticated Hackers Take Over Websites

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Drupal released security updates on November 18 to fix a critical flaw that could let attackers take over vulnerable websites without logging in. The bug, tracked as CVE-2026-132165, affects the installer included with Drupal core.

Under specific conditions, an attacker could use it to attempt to reinstall an existing site, leading to a takeover or remote code execution (RCE). Drupal urges administrators to update immediately.

The installer is designed to set up new Drupal sites. The risk arises when it can be used against a site that is already running. Remote code execution means an attacker could run their own code on the server.

Drupal says successful exploitation could expose private data and allow attackers to change site information. The Drupal Security Team rated the flaw 18 out of 25 on its own risk scale. The advisory says no account is required, but exploitation is complex, and the affected setup is uncommon.

Drupal Fixes Critical RCE Flaw

Drupal credits Anthropic’s open-source software scanner with finding the bug. The official security advisory lists proof of exploitation but does not report attacks in the wild.

This is separate from the Drupal Field UI RCE flaw disclosed in October and the Drupal core SQL injection bug CISA flagged as exploited in May. That confirmed activity involved a different vulnerability and does not establish that attackers are using the installer flaw.

Sites on Drupal 11.3.x should move to 11.3.22, while those on 11.4.x should install 11.4.13. Sites on 10.6.x should update to 10.6.22.

Drupal 11.2.x and earlier 11.x branches, along with 10.5.x and earlier 10.x branches, no longer receive security fixes. Drupal 8 and 9 are also out of support. Administrators on those versions should move to a supported branch.

The updates also fix CVE-2026-132166, a separate issue Drupal rates as moderately critical. Known as a gadget chain, it involves existing code that could be misused to run attacker-controlled code.

Drupal says it cannot be exploited on its own. A site would need another flaw that allows the application to rebuild PHP data from untrusted input.

Administrators who cannot patch immediately should follow Drupal’s guidance for securing the installer. Preventing the web server from writing to or changing permissions on settings.php blocks some attack paths, but it does not replace the update.

Drupal Steward blocks known attack paths, though the security team still advises customers to upgrade in case others are found. The Drupal 11.3.22 release notes also flag a change for new installations.

If settings.php is not writable during setup, the installer now shows an error instead of trying to change the file’s permissions automatically. For existing sites, the priority is to apply the security update and verify the installed version in Drupal’s status report.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs

The post Drupal Fixes Critical RCE Flaw That Could Let Unauthenticated Hackers Take Over Websites appeared first on Cyber Security News.