Skip to main content
Emerging Threats

Drupal patches RCE flaw, warns of swift exploitation.

Cluttered web development workstation with laptop and tools on a desk in a bright office setting.

CVE-2026-132165 is a critical remote code execution vulnerability in Drupal that can let anonymous users reinstall the CMS and take over vulnerable sites.

What the Drupal Security Team found and disclosed

The Drupal Security Team patched a critical remote code execution vulnerability tracked as CVE-2026-132165 after it was discovered by Anthropic's OSS Scanner. The team warned that "anonymous users can exploit it to reinstall the Drupal CMS." The advisory called the flaw critical because it can lead to site takeover or remote code execution under specific conditions.

The advisory explains that "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," the Drupal Security Team warned in a Wednesday advisory.

How the install.php flaw can be exploited

The vulnerability arises from the presence of the installer file (install.php) in Drupal core and the ability, under certain conditions, for an unauthenticated actor to invoke that installer. The security team noted that "some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php." That qualification indicates the exploit depends on server-side write or permission changes to the settings file.

In addition to CVE-2026-132165, Drupal addressed a separate but related issue on the same day: a moderately critical gadget chain vulnerability tracked as CVE-2026-132166. The team said that attackers with admin privileges can exploit that gadget chain "to gain remote code execution on a targeted site if the application deserializes untrusted data due to another security flaw." In other words, the gadget chain requires an initial condition—either admin privileges or a prior flaw that permits deserialization of untrusted data—to achieve code execution.

Patches, immediate mitigations, and the Drupal Steward WAF

  • Official updates: Administrators are instructed to upgrade to Drupal 10.6.22, 11.3.22, or 11.4.13.
  • Temporary hardening: For sites that cannot immediately upgrade, the advisory recommends securing the installer by blocking access to /core/install.php in the web server configuration or in the .htaccess file in the web root.
  • WAF protection: The paid Drupal Steward Web Application Firewall (WAF) service already protects subscribers from known attack vectors for this vulnerability, but those subscribers are nevertheless advised to upgrade in case other attack vectors are discovered.

The urgency of the patch is underscored by the Drupal Security Team's advance warning: "The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days," the security team said in a Monday advance warning. "The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users."

Related vulnerabilities and recent exploit activity

Drupal has been addressing multiple serious flaws this year. In May, the project confirmed active exploitation of an SQL injection vulnerability in the database abstraction API, tracked as CVE-2026-9082, which could allow attackers to escalate privileges, access sensitive information, or achieve remote code execution on unpatched servers.

More recently, Drupal warned that a critical access bypass vulnerability in the Commerce Core module (CVE-2026-118539) is being abused in attacks. The US Cybersecurity and Infrastructure Security Agency (CISA) has flagged five Drupal vulnerabilities as exploited in the wild since November 2021, two of which have also been abused in ransomware attacks.

What this means for technologists, government and research organizations, and enterprise webmasters

  • Technologists and security teams: Reserve time for core updates and apply the specified releases (10.6.22, 11.3.22, or 11.4.13) as soon as operationally feasible; block /core/install.php where immediate patching is not possible.
  • Government entities and educational or research institutions: Because the CMS "is commonly used by large organizations that manage multi-site installations and massive data structures," institutions should treat the advisory as high priority for multi-site patch planning and consider whether server file-permission configurations already mitigate some exploit paths.
  • Enterprise webmasters and paid WAF subscribers: Organizations using the Drupal Steward WAF service are protected from known attack vectors but should still plan upgrades in case new exploit paths are discovered.

Drupal's warnings and the record of active exploitation make clear that the window for attackers to build and deploy exploits can be short. With CVE-2026-132165 exploitable by anonymous users and the security team's explicit caution that "exploits might be developed within hours or days," administrators face a narrow, concrete task: patch, or block the installer, and verify server write and permissions configurations for settings.php.

Source: https://www.bleepingcomputer.com/news/security/drupal-patches-critical-rce-flaw-warns-exploits-may-surface-quickly/