CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Drupal core SA-CORE-2026-018: gadget chain, not directly exploitable on its own; fixed in 11.4.13, 11.3.22, 10.6.22

cve · CVE-2026-132166 single-source

Coverage
1
first 2026-11-18 → last 2026-11-19
Latest activity
2026-11-19
Drupal 11.4.13, 11.3.22, 10.6.22 fix an installer reinstall to takeover or RCE (SA-017, Critical); update now
Peak priority
notable
1 notable
Targets
technology
sectors: technology
Sources cited
5
3 hosts

Action items (1)

Do-now tasks recorded on the entries about CVE-2026-132166, newest first. Check the date before acting on an older one.

  • Update every Drupal site to 11.4.13, 11.3.22 or 10.6.22 now and move sites on end-of-life lines (Drupal 11.2.x and 10.5.x and below) to a supported branch, and where the update has to wait secure the installer as Drupal's instructions for securing install.php describe, because SA-CORE-2026-017 lets an attacker who reaches the installer attempt a reinstall that can end in site takeover or remote code execution.
    2026-11-18CVE-2026-132165 +1

Defender insights

What each entry about CVE-2026-132166 tells a defender to do, newest first.

2026-11-18NOTABLEDrupal 11.4.13, 11.3.22, 10.6.22 fix an installer reinstall to takeover or RCE (SA-017, Critical); update now

Exposure · detection

Story timeline

  1. 2026-11-18Drupal core 11.4.13, 11.3.22 and 10.6.22 fix CVE-2026-132165 (SA-CORE-2026-017, Critical): under specific conditions an attacker can use the installer to reinstall Drupal, which can lead to site takeover or remote code execution; the only workaround is securing the installer, and no exploitation is reported
    trending-vulnerabilitiesDrupal 11.4.13, 11.3.22, 10.6.22 fix an installer reinstall to takeover or RCE (SA-017, Critical); update now

Hunting pivots

Affected products
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-11-18/drupal-core-critical-release-2026-11-18-psa-2026-11-16 · ATT&CK page ↗

Entries about Drupal core SA-CORE-2026-018: gadget chain, not directly exploitable on its own; fixed in 11.4.13, 11.3.22, 10.6.22 (1)

2026-11-18 · view entry permalink →

NOTABLECVE-2026-132165 +1updatedNATOA2

Drupal core 11.4.13, 11.3.22 and 10.6.22 fix CVE-2026-132165 (SA-CORE-2026-017, Critical): under specific conditions an attacker can use the installer to reinstall Drupal, which can lead to site takeover or remote code execution; the only workaround is securing the installer, and no exploitation is reported

Drupal shipped its announced core security release on 2026-11-18. SA-CORE-2026-017 (CVE-2026-132165, rated Critical 18 of 25, with access complexity Complex, access none, exploit status Proof, meaning a proof of concept exists with documented methods for developing an exploit in the wild, and target distribution Uncommon, meaning only uncommon module configurations are exploitable) says that under specific conditions an attacker can use the installer to attempt to reinstall Drupal, which can lead to a site takeover or remote code execution (Drupal Security Team, 2026-11-18). SA-CORE-2026-018 (CVE-2026-132166, Moderately critical 14 of 25) is a gadget chain that Drupal says is not directly exploitable: a separate vulnerability must be present to let an attacker pass unsafe input to unserialize() (Drupal Security Team, 2026-11-18).

Both advisories cover core before 10.6.22, from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13, fixed in 11.4.13, 11.3.22 and 10.6.22; Drupal 11.2.x and below and 10.5.x and below are end-of-life and receive no security coverage (Drupal Security Team, 2026-11-18). The only workaround Drupal gives is to secure the installer; it adds that some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php, and that sites on Drupal Steward are already protected from SA-CORE-2026-017's known attack vectors (Drupal Security Team, 2026-11-18). The pre-announcement had warned that exploits might be developed within hours or days (Drupal Security Team, 2026-11-16); NCSC.ch's Security Hub rated exploitation unknown on 2026-11-17 (NCSC.ch, 2026-11-17), and neither advisory reports exploitation.

The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.

The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users.

Neither the Security Team nor any other party is able to release any more information about this vulnerability until the announcement is made.

Drupal Security Team (PSA-2026-11-16) 2026-11-16

Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution.

Drupal Security Team (SA-CORE-2026-017) 2026-11-18

This issue is not directly exploitable.

Drupal Security Team (SA-CORE-2026-018) 2026-11-18
Updaterun 2026-11-19T0355Z-intelactionsbodycvesevent_dateevidenceheadlineprioritysourcessourcing_notesummarytagstitleupdated_at

The release the pre-announcement described is out. Drupal published SA-CORE-2026-017 (CVE-2026-132165, Critical 18 of 25) and SA-CORE-2026-018 (CVE-2026-132166, Moderately critical 14 of 25, not directly exploitable) on 2026-11-18, fixed in Drupal 11.4.13, 11.3.22 and 10.6.22 (Drupal Security Team, 2026-11-18, Drupal Security Team, 2026-11-18). SA-CORE-2026-017 says an attacker can use the installer to attempt to reinstall Drupal, which can lead to a site takeover or remote code execution, and the only workaround is to secure the installer (Drupal Security Team, 2026-11-18). The 18 of 25 rating in the pre-announcement is SA-CORE-2026-017's; neither advisory reports exploitation.

vulnerability18 Nov 05:09Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • drupal.org3 (60%)
  • advisories.ncsc.nl1 (20%)
  • security-hub.ncsc.admin.ch1 (20%)