Skip to main content
All incident reports
Incident report

Drupal warns of critical flaw letting unauthenticated attackers take over sites

Drupal's maintainers have disclosed a critical vulnerability, CVE-2026-132165, that in some configurations lets an anonymous attacker reinstall a site through its installer and take it over or run code. Fixed releases are available and no exploitation has been reported, but the project warns exploit code could follow within hours or days.

· First published

The short version

  • The flaw. CVE-2026-132165 is rated critical and can be used by an unauthenticated attacker to take over a vulnerable Drupal site or execute code on it. In certain cases the attacker reaches this through Drupal's installer, which can be used to reinstall the site.
  • The warning. Drupal says exploits may be developed within hours or days and that operators should not assume their site is safe. It has published fixed releases and separate instructions for sites that cannot update straight away.
  • Dutch assessment. The Netherlands' National Cyber Security Centre (NCSC) issued its own warning, rating the likelihood of abuse as medium and the potential damage as large. It says unresolved flaws could let an attacker view, change or delete data or place malicious content.
  • Exploitation status. No abuse of this vulnerability has been reported so far. Earlier Drupal security flaws have been exploited in attacks over the past few years, according to the report.

Timeline

DateEvent
19 NovDrupal publishes a critical security release for CVE-2026-132165 and warns that exploits may appear within hours or days.
19 NovThe Netherlands' National Cyber Security Centre issues a separate warning, assessing likelihood of abuse as medium and potential damage as large.

What the vulnerability allows

Drupal's maintainers describe CVE-2026-132165 as critical. In certain cases an attacker can use the installer to reinstall Drupal, which allows the site to be taken over or code to be run on the server. The attacker needs no account on the site, so anyone who can reach it can attempt the attack.

The project says the problem affects several Drupal configurations, which is why it tells operators not to assume their installation is safe. Its standard advice for critical issues is to install the security updates quickly, because working exploit code can be produced within hours or days of disclosure.

Who is affected and what to install

More than a million websites run Drupal. Fixed versions are 11.4.13, 11.3.22 and 10.6.22. Drupal 10.5.x and earlier are end-of-life and no longer receive security updates.

For sites that cannot update immediately, Drupal has published instructions for protecting the installer. The NCSC's separate warning rates the chance of abuse as medium and the possible damage as large, and notes that unpatched flaws of this kind can lead to data being viewed, altered or deleted, or to harmful content being placed on the site.

Context

Drupal has been a repeated target. Several security flaws in the content management system have been exploited in attacks in recent years, though the report gives no evidence of exploitation of this one.

What is not known yet

  • Which specific Drupal configurations and modules are exposed, beyond the project's statement that several are affected.
  • Whether anyone has already attempted to use the installer against sites running the vulnerable code.
  • Who might carry out attacks and what they would be after.
  • How many of the million-plus Drupal sites are actually running a vulnerable version rather than an end-of-life branch.
  • Whether the installer-protection instructions fully block the attack or only reduce exposure.

What to do

If you run Drupal

  1. Update to 11.4.13 now if you are on the 11.4 branch, and check Drupal's advisory for the fixed release matching any other supported branch you run.
  2. Identify any site still on 10.5.x or older and plan its move to a supported branch, since those versions will not receive a fix.
  3. Do not assume the site is safe because it is unusual or lightly customised; the project says several configurations are affected.

If you cannot update immediately

  1. Apply Drupal's published instructions for securing the installer.
  2. Review web server and application logs for unexpected use of installer paths.

For everyone else

  1. Keep internet-facing content management systems on supported releases, because end-of-life branches leave you with no patch to apply.
  2. Treat critical CMS advisories as time-sensitive: exploit code can appear within hours or days, so schedule the update for the same working day.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

We email you about this topic only; unsubscribe any time. See our Privacy Policy.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.