TL;DR
On November 18, 2026, the Drupal team patched two core security bugs. First, CVE-2026-132165 in advisory SA-CORE-2026-017 allows Drupal remote code execution via the site installer. Second, CVE-2026-132166 in advisory SA-CORE-2026-018 exposes a medium-risk PHP gadget chain.
- Vulnerabilities: 2 flaws (CVE-2026-132165, CVE-2026-132166)
- Highest severity: Awaiting analysis
- Status: No confirmed exploitation yet
- Action: See vendor advisories
| CVE | Status |
|---|---|
| CVE-2026-132165 | Not exploited |
| CVE-2026-132166 | Not exploited |
Why It Matters
Web tracker W3Techs notes that Drupal runs about 0.6 percent of all websites. In fact, TechnologyChecker counts nearly 159,000 live Drupal sites across major firms and public agencies. Because threat actors scan for open CMS bugs, unpatched sites face full takeover risks. So far, researchers have seen no active attacks in the wild and no public exploit code.
How the Attack Works
Site Installer Bug
Anthropic’s OSS Scanner found CVE-2026-132165 under ID ANT-2026-GMRPK0BU. By design, Drupal core ships with an install.php file for initial site setup. Under rare conditions, remote attackers can call this script to reinstall Drupal and gain Drupal remote code execution. However, read-only permissions on settings.php block many attack paths.
Object Gadget Chain
Researcher Drew Webber reported CVE-2026-132166 in Drupal core. This bug links internal PHP methods into a gadget chain. On its own, the chain causes no harm. Yet if another plugin passes unsafe data to PHP’s unserialize function, attackers can run arbitrary code.
Affected Versions
Both bugs impact Drupal core before 10.6.22, versions 11.0.0 to 11.3.21, and versions 11.4.0 to 11.4.12. Meanwhile, Drupal 8, Drupal 9, 10.5.x, and 11.2.x are end-of-life and get no security fixes.
Patch and Mitigation Steps
Site owners should update to Drupal 11.4.13, 11.3.22, or 10.6.22 right away to stop Drupal remote code execution attacks. Next, teams that cannot patch yet must lock write access on settings.php and block access to install.php. While Drupal Steward filters known vectors, patching stays vital.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!