SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

Drupal Patches Critical Core RCE Flaw CVE-2026-132165, Warns of Fast Exploitation

Drupal has released core updates for critical remote code execution flaw CVE-2026-132165 and warned that exploits may appear within hours or days. Blocking /core/install.php is the interim mitigation.

Drupal Patches Critical Core RCE Flaw CVE-2026-132165, Warns of Fast Exploitation

The Drupal security team has released core updates for a critical remote code execution vulnerability, CVE-2026-132165, and has warned site owners that working exploits could appear within hours or days of disclosure. The advisory, SA-CORE-2026-017, was published on November 18 and covers all supported Drupal 10 and 11 branches.

A second advisory released alongside it, SA-CORE-2026-018, fixes a related moderately critical issue, CVE-2026-132166, which the Drupal team describes as a gadget chain that is not directly exploitable on its own. No attacks exploiting either flaw had been reported at the time of writing, according to The Hacker News.

What happened

Drupal gave advance notice of the release in public service announcement PSA-2026-11-16, setting a release window of 17:00 to 21:00 UTC on November 18 and cautioning that exploits might be developed quickly. The fixed versions were published in that window.

The advisory’s mitigation guidance centers on the core installer script, and The Hacker News describes the issue as an installer flaw that could let unauthenticated attackers take control of sites. The Drupal team has not published technical details of the root cause, and none are given here. According to the advisory, the vulnerability was identified with help from Anthropic’s open-source scanning effort, and it credits several reporters including Lee Rowlands.

Who is affected

According to SA-CORE-2026-017, the following Drupal core versions are vulnerable:

BranchVulnerableFixed
Drupal 10Earlier than 10.6.2210.6.22
Drupal 11.0 to 11.311.0.0 up to but not including 11.3.2211.3.22
Drupal 11.411.4.0 up to but not including 11.4.1311.4.13

The advisory does not state whether end-of-life branches are affected. Organizations running unsupported Drupal versions should assume exposure until they confirm otherwise. Sites protected by the Drupal Steward web application firewall service are covered against the known attack vectors, according to the Drupal team.

Severity and exploitation

Drupal rates CVE-2026-132165 as Critical, scoring 18 out of 25 on its own risk scale. The vector describes complex access conditions but full impact on confidentiality and integrity, and marks the exploit status as proof of concept, meaning a working demonstration exists. Drupal’s scale is not CVSS and the two scores are not directly comparable.

BleepingComputer did not report exploitation in the wild, and The Hacker News said no attacks had been reported. Past critical Drupal core flaws have been weaponized soon after patches were released, which is why the security team issued its warning in advance.

What defenders should do now

  1. Upgrade Drupal core to 10.6.22, 11.3.22 or 11.4.13, depending on the branch in use. This addresses both SA-CORE-2026-017 and SA-CORE-2026-018.
  2. If an immediate upgrade is not possible, block access to /core/install.php in the web server configuration or .htaccess, as the advisory recommends.
  3. Inventory every Drupal site, including marketing, campaign and staging sites, which are often missed in patch cycles.
  4. Review web server logs for requests to /core/install.php on sites that are already installed, and treat unexpected hits after November 18 as suspicious.
  5. Check for unexpected administrator accounts, configuration changes or new PHP files on sites that were exposed before patching.
  6. Confirm that WAF rules covering the installer path are active where a managed firewall is in use.

SCVM analysis

The Drupal team’s decision to pre-announce the release and warn of quick exploitation is a strong signal that defenders should treat this as an emergency patch rather than part of a monthly cycle. A proof of concept already exists according to the advisory’s own rating, and diffing the patch narrows the work for attackers. The installer script should never be reachable on a production site after setup, so the recommended block is also good hygiene worth keeping after the upgrade. The credit to an automated scanning program is another example of AI-assisted discovery bringing serious bugs to light in mature open-source code, a trend that is likely to increase the pace of critical disclosures that maintainers and defenders must absorb.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SCVM Newsroom

The SCVM Newsroom is SecureCyberVM's AI-assisted news desk. It tracks vulnerability disclosures, exploitation reports and security advisories from trusted sources, enriches them with NVD, EPSS and CISA KEV data, and publishes defender-focused briefings under our editorial policy.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.