As reported by The Hacker News, Drupal has patched a critical installer vulnerability — CVE-2026-132165 — that could allow unauthenticated attackers to trigger site reinstallation and potentially achieve remote code execution. The flaw is notable not just for its severity, but for how it was found: by Anthropic's automated OSS Scanner, a development we expect to reshape open-source security workflows.

Security Impact: As reported by The Hacker News, Drupal has patched a critical installer vulnerability — CVE-2026-132165 — that could allow unauthenticated attackers to trigger site reinstallation and potentially achieve remote code execution.

Vulnerability Details

FieldValue
CVECVE-2026-132165
SeverityCritical (18/25 on Drupal risk scale)
Attack VectorUnauthenticated, network-accessible
ImpactSite takeover, remote code execution
Affected VersionsDrupal < 10.6.22; 11.0.0–11.3.21; 11.4.0–11.4.12
Fixed Versions10.6.22, 11.3.22, 11.4.13
Active ExploitationNot observed; PoC exists; exploitation rated complex
Patch AvailableYes — released November 18, 2026

Why This Matters Beyond the CVE

The core issue is architectural and familiar to anyone who has audited CMS deployments: installation scripts that persist post-setup. Drupal ships /core/install.php in every core distribution, and default .htaccess rules do not restrict access to it. This means the attack surface exists on virtually every Drupal site that hasn't explicitly hardened this path — a configuration gap that many administrators would never consider.

What elevates this advisory is the discovery mechanism. Anthropic's OSS Scanner — launched in October 2026 — identified the flaw automatically and reported it with a reproducer and candidate patch, with no human review in the loop. The Drupal Security Team has separately noted a surge in AI-generated security reports. This is a double-edged development:

  • Benefit: More vulnerabilities surfaced faster, particularly in under-audited open-source projects.
  • Risk: Volume of reports can overwhelm maintainer teams, and AI-discovered flaws with PoCs may accelerate adversarial exploitation if disclosure timelines slip.

Who Is Most Exposed

  • Organizations running EOL Drupal branches — nearly 29% of reporting sites (≈154,000) run Drupal 10.5.x or earlier, 8, or 9. These receive no fix.
  • Self-hosted Drupal deployments where administrators haven't blocked /core/install.php via web server rules.
  • Hosting providers offering one-click Drupal installs that leave default configurations intact.
  • Configurations where the web server can write to settings.php — these face the most direct RCE path.

Shield53 Recommendations

Immediate Actions

Shield53 Recommendations
Patch now: Update to Drupal 11.4.13, 11.3.22, or 10.6.22 depending on your branch. Do not delay for testing windows — the PoC exists and exploitation complexity is rated as the primary barrier.
Block the installer regardless of patch status: Add a deny rule for /core/install.php in your web server configuration (nginx, Apache) or .htaccess. The file should not be web-accessible on any production site.
Verify settings.php permissions: Ensure the web server user cannot write to or modify sites/default/settings.php. This blocks the most severe exploit path even if the installer is reachable.
EOL migration plan: If you're running Drupal 10.5.x or earlier, 8, or 9 — you have no patch. Treat this as an urgent migration trigger, not a backlog item. Drupal 10 and 11.3.x lose security support entirely in December 2026.
Detection: Monitor access logs for requests to /core/install.php from non-internal IPs. Any POST requests or 200 responses on this path in production warrant immediate investigation.
WAF / Drupal Steward: If you use Drupal Steward or a WAF with virtual patching, confirm coverage is active — but still patch the underlying code.
Strategic note: Persistent installer scripts are a recurring attack surface across CMS platforms. This Drupal advisory is a reminder to audit every web application in your stack for setup, diagnostic, or admin scripts that should have been removed or restricted post-deployment.