Key facts
- Unauthenticated users can exploit CVE-2026-132165 to attempt a reinstallation of the Drupal CMS, potentially leading to remote code execution or full site takeover.
- The Drupal Security Team warned on November 17, 2026, that exploits for these vulnerabilities could be created within hours or days.
- The vulnerability in CVE-2026-132165 is located in the install.php file included with Drupal core.
- Anthropic's OSS Scanner discovered the CVE-2026-132165 flaw, which is also identified as ANT-2026-GMRPK0BU.
On Nov. 18, 2026, the Drupal Security Team shipped fixes for a critical remote code execution flaw in Drupal core, tracked as CVE-2026-132165..
Unauthenticated users can exploit the flaw to trigger a fresh installation attempt through the install.php file that ships with Drupal core, potentially resulting in remote code execution or total site compromise. The security team rated the vulnerability critical at 18 out of 25, and Anthropic’s OSS Scanner discovered it under the tracking code ANT-2026-GMRPK0BU..
The Drupal Security Team issued its warning on Nov. 17, 2026, saying working exploits could appear within hours or days, and urged administrators to make time for core updates rather than assume a longer buffer. Techgenyz reports the official advisory has not confirmed active exploitation of CVE-2026-132165 or CVE-2026-132166. Researchers do not know how often the conditions needed for exploitation occur in real setups, so the project treats the issue as urgent..
Administrators should move sites to Drupal 10.6.22, 11.3.22, or 11.4.13 to close the flaw. Teams that cannot upgrade right away can block access to /core/install.php using .htaccess rules or web server configuration, but the security team describes that block as a short-term control rather than a permanent substitute for the patch. It also advises securing or deleting the installer after updating, and says keep the file out of reach by removing it or configuring Composer so it does not restore the file..
Some exploit paths close automatically when the web server cannot modify file permissions or write to settings.php. Drupal Steward’s WAF service protects against known attack routes for this flaw, though the security team still urges upgrading instead of relying on the service alone..
The team also patched CVE-2026-132166, a gadget chain vulnerability that can lead to remote code execution for users who hold administrator privileges when another issue allows deserialization of untrusted data. That companion issue carries a moderately critical rating of 14 out of 25..
Drupal runs sites for federal agencies and research universities, plus media outlets and educational groups. Government users include NASA, national portals, the European Commission, and the U.S. Internal Revenue Service. CISA has listed five Drupal vulnerabilities under active exploitation since November 2021, two tied to ransomware..
In May 2026, Drupal said CVE-2026-9082, an SQL injection flaw in the database abstraction layer, was under active exploitation, and that issue affected only sites running PostgreSQL databases. The project has also warned of active abuse targeting CVE-2026-118539, a critical access bypass flaw in the Commerce Core module..
A prior high-severity flaw, PSA-2026-05-18, required patching across every supported core branch on May 20, 2026, from 17:00 to 21:00 UTC. It rated 20 out of 25 and did not require authentication. Berkeley’s Information Security Office said attackers could reverse-engineer the patch and have working exploit code almost immediately, and any institution still unpatched 24 hours after an advisory goes live should treat itself as a target..
Tech Times reported that The Register has found no Drupal flaw exploited in the wild since 2019, so the May advisory marked the first highly critical issue in years. Its scoring profile parallels the 2018 Drupalgeddon2 flaw, CVE-2018-7600, which started automated scans of every reachable Drupal site and left more than 100,000 sites confirmed vulnerable before patches became common..
All supported branches needed patching for that flaw, covering 11.3.x, 11.2.x, 10.6.x, and 10.5.x, with manual patch files offered temporarily for end-of-life 8.9 and 9.5 branches. Drupal 7 was unaffected, and the flaw lived in core rather than in Drupal CMS. The University of Michigan’s Safe Computing office asked staff to set aside time before the May 20 patching window, and hosting provider amazee.io staged WAF and content-delivery virtual patches as a partial, temporary fix..
Versions of Drupal 11.2.x and earlier are end-of-life and get no security coverage, and Drupal 8 and Drupal 9 no longer receive security coverage. Teams running unsupported minor releases including 11.1, 11.0, 10.4, 10.3, 10.2, 10.1, or 10.0 need at least version 11.1.9 or 10.4.9 before they can apply the security patch..
The Anthropic OSS Scanner is a no-cost, voluntary AI scanning tool that generates automated reports, but its findings may include false positives and do not take the place of manual review. Techgenyz says AI-assisted scanning keeps getting better at finding serious flaws in open-source code, which helps defenders but shrinks the time between discovery and exploitation. Drupal sites often delay core updates since testing, custom modules, and staging workflows take time, and installer files left accessible after deployment keep creating risk..
Patches are available for the supported branches, and the Drupal Security Team urges operators to apply them rather than rely on temporary blocks. After installation completes, the team advises securing the installer..

Join the discussion