Drupal Patches Core RCE Flaw CVE-2026-132165 in Site Installer

Drupal patched CVE-2026-132165, a core flaw that under rare conditions lets remote attackers reinstall a site through install.php and gain code execution.
Table of Contents
    Add a header to begin generating the table of contents

    Drupal released security updates on November 18 that fix CVE-2026-132165, a core remote code execution flaw in the site installer. Under rare conditions, a remote attacker can call install.php to reinstall Drupal and gain code execution. No active attacks and no public exploit code have been seen.

    SA-CORE-2026-017 and the install.php Reinstallation Path

    Advisory SA-CORE-2026-017 covers CVE-2026-132165. The flaw lets a remote attacker reach the installer script, run the installation routine again on a site that is already set up, and turn that into code execution. Drupal says the conditions required are rare.

    Read-only permissions on settings.php block many attack paths. Sites with that file set to read-only are therefore less exposed to the reinstallation route.

    The installer is normally used once, when a site is first built, and is not expected to be reachable afterward. A flaw that lets an outsider invoke it on a live site turns a setup tool into a way to overwrite the site’s state, which is the reason the maintainers rated the consequence as remote code execution even though the conditions are rare. Drupal has not published the specific combination of conditions, so operators cannot easily judge whether their own configuration is the rare case.

    Anthropic’s OSS Scanner as the Source of the Finding

    Anthropic’s OSS Scanner found the flaw, tracked internally as ANT-2026-GMRPK0BU. That makes the issue the latest example of automated code-analysis tools turning up serious flaws in long-established open-source projects.

    Affected Versions and Which Drupal Lines Get Nothing

    The affected versions are Drupal core before 10.6.22, 11.0.0 through 11.3.21 and 11.4.0 through 11.4.12. Drupal 8, 9, 10.5.x and 11.2.x are end-of-life and receive no fixes. Sites on those lines cannot patch in place and have to move to a supported branch to get protection.

    A Second Advisory on a PHP Gadget Chain

    Advisory SA-CORE-2026-018 covers CVE-2026-132166, rated medium. It describes a PHP gadget chain in Drupal core that is harmless by itself. If another plugin passes unsafe data to unserialize(), the chain becomes a path to code execution. Drew Webber reported it.

    Why the Gadget Chain Depends on Other Code

    Because the chain needs a second component that feeds untrusted data into unserialize(), its real-world risk depends on the particular modules installed on a site. Core alone does not expose it, but an installed contributed module with the wrong behavior could complete the chain.

    Drupal rates CVE-2026-132166 as medium because it cannot be exploited by itself. The distinction between a flaw that is dangerous on its own and one that supplies a building block is a common one in PHP applications, where object deserialization has long been a path from a small bug to code execution once a suitable chain exists in the loaded code.

    Fixed Releases and the Size of the Exposed Population

    Updating to Drupal 11.4.13, 11.3.22 or 10.6.22 resolves the flaws. A report on the update cites about 159,000 live Drupal sites, which gives an idea of the population that run the platform, though the number of sites actually within the vulnerable range and the rare conditions is not known.

    Drupal’s earlier advisories this year covered different vulnerabilities, and CVE-2026-132165 is a new one. The “rare conditions” language limits the likelihood of widespread attacks, but a core flaw that allows reinstallation of a running site is the sort of bug that attackers tend to test once details are public.

    For site operators, the combination of a serious core bug, narrow conditions and a list of end-of-life branches with no fixes produces a split picture: supported branches have a clear update, while owners of old sites face a migration decision that no patch can resolve.

    Related Posts