Drupal core: remote code execution vulnerability (CVE-2026-132165, CVE-2026-132166) fixed in 11.4.13, 11.3.22, 10.6.22
CVE-2026-132165 CVE-2026-132166
Published 18/11/2026 20:23
Timeline
2 events over 21 min
- 18/11/2026 20:01ConfirmedNCSC-NL advisories+21 min
- 18/11/2026 20:23Published on WatchtowerPro CISO
In short
Drupal published two core advisories on 18/11/2026. SA-CORE-2026-017 (CVE-2026-132165) is rated Critical: under specific conditions an attacker can use the installer to try to reinstall Drupal, which can lead to site takeover or remote code execution. SA-CORE-2026-018 (CVE-2026-132166) is rated Moderately critical: a deserialization gadget chain that is not directly exploitable. Shodan estimates about 54,344 internet-facing Drupal servers worldwide, 18,145 of them in the EU (19/11/2026); how many run an affected version is not yet known.
How bad is it
Critical. Under specific, uncommon conditions an attacker could reinstall a vulnerable Drupal site through its installer and take it over or run their own code, without logging in.
Confirmed by the vendor or a CERT - no exploitation reported yet.
Severity score
No CVSS score published yet
CVE-2026-132165, CVE-2026-132166: no score published yet. A missing score is never read as 0.
What an attacker needs
- Internet access to itNot published yet
- A loginNot published yet
- A user to clickNot published yet
- Special settingsNot published yet
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Run their own code on the system
Type: remote code execution.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- Drupal core below 10.6.22 (both CVEs).
- Drupal core from 11.0.0 up to but not including 11.3.22 (both CVEs).
- Drupal core from 11.4.0 up to but not including 11.4.13 (both CVEs).
Fixed in
- 11.4 branch: 11.4.13 (released 18/11/2026 17:44 Amsterdam time)
- 11.3 branch: 11.3.22
- 10.6 branch: 10.6.22 (released 18/11/2026 17:47 Amsterdam time)
What to do now
- Update Drupal core to the fixed version for your line: 11.4.13 (11.4.x), 11.3.22 (11.3.x) or 10.6.22 (10.6.x).
- If you run Drupal 11.2.x or older, 10.5.x or older, or Drupal 8/9, move to a supported, fixed release; Drupal states these lines are end-of-life.
- Until updated, follow Drupal's guide 'Securing the installer (install.php)' on drupal.org, and where possible make sure the web server cannot write to or change permissions on settings.php.
- Customers of Drupal Steward get protection against some known attack vectors of SA-CORE-2026-017, which does not replace the update.
- These interim measures reduce exposure and do not make a site safe; only the update fixes the flaw.
- After updating, note that 11.4.13 and 10.6.22 change installer behaviour: if settings.php is not writable, the installer now shows an error instead of fixing permissions itself. Drupal says this does not affect existing sites but does affect new installations.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 5 open questions, followed up as sources answer and all 5 sources with their dates. And technology matching: which of your systems run Drupal, at which version, fixed or not - and what each one needs.
Main sources
NCSC-2026-0507 [1.00] [M/H] Kwetsbaarheden verholpen in Drupal core CERT · Drupal core - Critical - Remote code execution - SA-CORE-2026-017 Research · Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-018 Research