Drupal vulnerability CVE-2026-132165 can lead to takeover
Part of the CVE-2026-132165 story · since 18 Nov
- Wed 18 Nov, 19:00 UTC. cybersixt, first report. Drupal vulnerability CVE-2026-132165 can lead to takeover. This article, 1st of 1.
The Drupal Security Team released fixes on Wednesday for a flaw in the content management system's own installer that can end in a site takeover or remote code execution. The advisory, SA-CORE-2026-017, tracks it as CVE-2026-132165 and rates it critical on Drupal's own scale, at 18 out of 25.
Drupal core ships with an install.php file used to set a site up. “Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal,” the advisory says. “This can lead to a site takeover or remote code execution.” It does not describe the conditions. Some exploit paths are closed, it adds, if the web server cannot write to settings.php or change its permissions.
The team had warned site owners two days earlier. A public service announcement on Monday asked them to reserve time for the release “because exploits might be developed within hours or days”, and said: “More than one configuration is affected, so do not assume your site is safe.”
Affected versions and fixed releases
Every supported branch is affected. The advisory lists the fixed releases:
- Drupal 11.4.x: update to 11.4.13
- Drupal 11.3.x: update to 11.3.22
- Drupal 10.6.x: update to 10.6.22
Drupal 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 are end-of-life and get no fix. The announcement told those sites to apply the interim steps below and update as soon as possible. It also said Drupal 12.0.0-beta3 and 11.5.0-beta1 are affected.
The release notes for 11.4.13 describe one visible change. If settings.php is not writable during a new installation, the installer used to try to fix the file's permissions by itself; it now shows an error. Existing sites are not affected by that change, the notes say.
How Drupal scores it
The advisory's risk string reads AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon. Drupal's definitions turn that into four statements: the attack is complex or highly specific, it needs no authentication (“all/anonymous users”), a proof of concept exists, and “only uncommon module configurations are exploitable”. The scale is Drupal's own, not CVSS. The advisory does not report attacks on live sites.
The flaw was “discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU”, the advisory says.
If you cannot update yet
The advisory points sites that cannot upgrade immediately to Drupal's guide to securing the installer, and recommends the same step after upgrading. The guide, updated on Wednesday, gives three options:
- Block it in the web server configuration, the recommended route. On Apache, add
Require all deniedinside a<Location "/core/install.php">block. On Nginx, addlocation ^~ /core/install.php { return 404; }inside theserverblock. The guide warns against an exact match (location =), which on some servers still lets/core/install.php/foorun the installer. - Block it in
.htaccess(Apache only) withRequire all deniedinside<Files "install.php">. On Composer-based sites that file is replaced on every scaffold run, so the lines have to be appended through the scaffold file mapping. - Delete
core/install.php. Composer puts it back each time it installs or updates core, so the guide suggests removing it again from Composer scripts.
Blocking install.php does not affect updates, the guide says, because update.php is a separate script. Drupal “does not block it for you”: the .htaccess file that ships with core allows access to the installer on purpose.
Sites behind Drupal Steward, the security team's paid web application firewall service, “are already protected from some known attack vectors, but the protection offered will not cover all possible exploits”, according to the advisory, which tells them to upgrade as well.
The second advisory
The same releases fix CVE-2026-132166, described in SA-CORE-2026-018 and rated moderately critical. It is a “gadget chain”: code in core that could be used for remote code execution only if another vulnerability lets the site deserialize untrusted data. “This issue is not directly exploitable,” that advisory says.
Still to come are the patched pre-release builds. The security team said new beta or release candidate versions of Drupal 12.0.0 and 11.5.0 will follow the updates for the supported branches.
How the story developed
1 article from 1 outlet since 18 Nov. Still developing; the latest report was 9 minutes ago. This was the first report.
- Wed 18 Nov, 19:00 UTC. cybersixt, first report. Drupal vulnerability CVE-2026-132165 can lead to takeover. This article, 1st of 1.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Wed 18 NovDay 01
- Drupal vulnerability CVE-2026-132165 can lead to takeover19:00 · cybersixt · First report · This article, 1st of 1
Sources
- Drupal advisory SA-CORE-2026-017Primary sourcedrupal.org
- Drupal advisory SA-CORE-2026-018Primary sourcedrupal.org
- Drupal announcement PSA-2026-11-16Primary sourcedrupal.org
- Drupal 11.4.13 release notesPrimary sourcedrupal.org
- Securing the installer guidePrimary sourcedrupal.org
- Drupal security risk levelsdrupal.org
- Drupal Stewardnew.drupal.org
More reporting
- Visa data breach claim: supplier blamed as n0n names 5918 Nov
- nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published18 Nov
- LUKSO email recovery flaw lets attacker drain 300 profiles18 Nov
- Valcour security incident takes Vermont police system offline18 Nov
- Airbyte Cloud taken offline after cyberattack, syncs halted18 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS