Drupal's Installer RCE: Anthropic's AI Scanner Found the Bug, and Your /core/install.php Is Still Reachable

Drupal's Installer RCE: Anthropic's AI Scanner Found the Bug, and Your /core/install.php Is Still Reachable

Drupal's Installer RCE: Anthropic's AI Scanner Found the Bug, and Your /core/install.php Is Still Reachable

Drupal has patched a critical vulnerability that lets an attacker with no credentials reinstall a site under specific conditions — a path that ends in full site takeover or remote code execution. The flaw, tracked as CVE-2026-132165, was disclosed November 18 with fixed releases for every supported branch. The project rates it 18 out of 25 on its own risk scale, records an existing proof-of-concept exploit, and calls exploitation "complex" — but no attacks have been reported so far, which is exactly the window the Drupal Security Team asked site owners to use: "exploits might be developed within hours or days" was the warning in Monday's advance notice.

The mechanics are simple, which is what makes them dangerous. Drupal core ships an installer at /core/install.php, and that file stays on the site after installation. Core's default .htaccess rules do not block requests to it — blocking is left to each individual site. Under specific conditions, an unauthenticated attacker can use the installer to attempt a reinstall of Drupal; successful paths end with the attacker controlling the site or executing code on the server. Some exploit paths are mitigated where the web server cannot write to, or change permissions on, settings.php. Affected versions are every release below 10.6.22, Drupal 11 from 11.0.0 before 11.3.22, and 11.4.0 before 11.4.13. On the same day, Drupal also fixed a moderately critical admin-gadget-chain flaw, CVE-2026-132166, exploitable if the application deserializes untrusted data.

Two things make this story bigger than one CVE. First, the finder: the bug was discovered by Anthropic's OSS Scanner, the automated AI service the company launched October 8 to probe opted-in open-source projects, with findings — each carrying a reproducer and often a candidate patch — going to maintainers without human review. It is the second AI-found critical web bug this week, after Java4Shell in OpenJDK, and the second critical RCE in Drupal core in two months, after the Field UI flaw patched October 14. Second, the maintenance reality behind it: on November 2, Drupal's security team said a surge of reports it attributes to AI tools is more than its funding can sustain, and announced security coverage for core minor versions will shrink from 12 months to 8 starting in 2027. In the week of November 8, about 29 percent of Drupal sites reporting usage data — roughly 154,000 of 528,000 — were running end-of-life branches that receive no fix for this flaw at all.

What Should You Do?

  1. Update immediately: Drupal 11.4.x → 11.4.13, 11.3.x → 11.3.22, 10.6.x → 10.6.22. If you're on EOL branches (11.2 and earlier, 10.5 and earlier, Drupal 8/9), you get no patch — treat this as the upgrade trigger.
  2. Block the installer regardless: add a deny rule for /core/install.php at the web server or in .htaccess, or remove the file and keep it removed via Composer scripts. Updating alone does not remove the attack surface for the next installer bug.
  3. Verify settings.php permissions: ensure the web server user cannot write to or chmod the file — that closes the exploit paths the advisory says are mitigated.
  4. If you use Drupal Steward, update anyway. The paid WAF service already blocks known attack vectors, but the team explicitly warns other vectors may emerge.

The WAF Angle

This is the rare vulnerability where the WAF story is stated by the vendor itself: Drupal Steward — a Web Application Firewall offered by the Drupal project — already blocks the known attack vectors for this exact flaw. A WAF can do this well because the attack signature is structural: /core/install.php should never receive requests on a finished site, so a one-line virtual-patch rule (block requests to /core/install.php) converts a complex exploit into a 403, no matter which gadget path the attacker takes. Drupal's own guidance — deny the installer path at the web server or in .htaccess — is the same control, applied one layer down. The broader lesson connects to the Drupal Commerce access bypass under active attack in October: when your CMS's security team is shrinking coverage windows and 29% of sites run dead branches, a WAF's ability to hot-patch access-control and path-exposure flaws is the compensating control that keeps unpatchable sites survivable.

Sources