Skip to content

The publication for web craftspeople Sunday, 22 November 2026

Security

Drupal Patches a Critical Flaw Already Under Active Exploitation

Drupal shipped a security release on November 18, 2026 fixing SA-CORE-2026-017, a critical remote code execution flaw via the installer script that is already being exploited in the wild. A second flaw, SA-CORE-2026-018, closes off a deserialization chain.

Drupal corrige une faille critique d'exécution de code déjà exploitée

On November 18, 2026, the Drupal Security Team shipped an update covering every supported core branch. Two advisories ship alongside it: SA-CORE-2026-017, rated “highly critical” with an exploit already seen in the wild, and SA-CORE-2026-018, a moderate-severity deserialization chain. Both flaws hit a still-large installed base, and the announced patch window (17:00-21:00 UTC) left little room for teams that hadn’t planned ahead.

SA-CORE-2026-017: install.php reopens the door

The more serious flaw, tracked as CVE-2026-132165, abuses the install.php script to attempt a site reinstallation. On some configurations, that reinstallation leads to a full takeover or remote code execution. Drupal notes that only uncommon configurations are affected, but an exploit is already circulating, which changes the priority: this isn’t a convenience patch, it’s a risk window open from the moment of disclosure.

SA-CORE-2026-018: a chain, not a front door

The second flaw, CVE-2026-132166, isn’t exploitable on its own. It provides a remote-code-execution vector for anyone who already has a way to deserialize untrusted data on the site — through a third-party module, for instance. That makes it less urgent in isolation, but critical again the moment it combines with another vulnerability, which is why it ships alongside SA-CORE-2026-017 rather than on its own schedule.

AdvisorySeverityCVEVectorKnown exploit
SA-CORE-2026-017Highly critical (20/25)CVE-2026-132165install.php, reinstallationYes
SA-CORE-2026-018Moderately critical (14/25)CVE-2026-132166Deserialization chainNo, but combinable

Update without waiting

The update procedure itself hasn’t changed, but the gap between reading this and acting on it matters more than usual:

composer update drupal/core --with-all-dependencies
drush updatedb
drush cache:rebuild

Teams that manage updates through an external patch pipeline should confirm the latest fixed release for their branch was actually applied, not merely scheduled.

An exploit already circulating before a fix ships turns a planned update into an immediate risk window.

Drupal notes that sites protected by Drupal Steward already have mitigation against known vectors. That protection doesn’t excuse skipping the update: other advisories may have shipped the same day without that coverage.

Teams running Drupal on shared hosting or on a standard Drupal stack should compare their hardening policy to the one already laid out for WordPress: both ecosystems converge on the same reflexes — automatic core updates, removing exposed install scripts, logging access attempts to install.php. The previous critical alert on the Webform module followed the same coordinated-disclosure pattern, as covered in the article on that flaw.

Key takeaways

Two advisories fix, on November 18, 2026, a remote code execution flaw already under active exploitation (SA-CORE-2026-017) and a deserialization chain that only turns dangerous in combination (SA-CORE-2026-018). Updating Drupal core to the latest fixed release for every supported branch remains the one action that matters.

An exploit already active at disclosure time is the signal that should jump an update to the top of the stack, ahead of the rest of the sprint. It’s also a reminder that applies to any CMS: real protection was never the patch itself, it’s the routine that applies it within hours instead of weeks. — Simon Janvier

Further reading: the full advisory on drupal.org.

Read next