Critical Drupal Installer Flaw Now Exploited: Update Core Today
Attackers are already abusing a highly critical Drupal core flaw that lets them hijack the installer and take over sites. Update to 10.6.22, 11.3.22 or 11.4.13 now, or block install.php.
In this article
If your organisation, school, agency or media house runs its website on Drupal, this one needs attention today. On 18 November 2026 the Drupal Security Team released fixes for a highly critical remote code execution flaw in Drupal core, and it has since updated its advisory to say it received a report of the flaw being exploited on live sites from 19 November. This article explains what the bug does, which versions are affected and exactly what site owners and their web developers should do.
Key takeaways
- The flaw, tracked as CVE-2026-132165 (advisory SA-CORE-2026-017), abuses Drupal’s built-in installer to attempt to reinstall a site, which can lead to full site takeover or remote code execution.
- It can be triggered by anonymous visitors under specific conditions; no login is needed.
- Fixed versions are Drupal 10.6.22, 11.3.22 and 11.4.13.
- If you cannot update immediately, block public access to /core/install.php.
- Exploitation on live sites was reported from 19 November 2026, so treat this as urgent.

What happened
Drupal ships with an install.php file that is used once, when a site is first set up. According to the Drupal Security Team, under specific conditions an attacker can call that installer on an already-running site and try to reinstall Drupal. A successful attempt can hand the attacker control of the site or let them run their own code on the web server.
The team had issued an advance warning on the Monday before the release, telling administrators to reserve time for core updates because exploits might be developed “within hours or days”. That warning has proved accurate: the advisory now carries an update stating that the team received a report of exploitation on live sites as early as 19 November 2026 at 19:00 UTC.
The vulnerability was discovered by Anthropic’s OSS Scanner, an automated tool that looks for security bugs in open-source software, and was reported alongside members of the Drupal community.
A second, less severe fix
The same release also addressed a moderately critical “gadget chain” issue, CVE-2026-132166. BleepingComputer reports that it could let an attacker who already has administrator rights reach remote code execution if another flaw causes the site to process untrusted serialised data. It is less urgent on its own, but it is fixed by the same updates.
Who is affected
Drupal is widely used by governments, universities, research institutions, large enterprises and media organisations because it handles complex, multi-site setups well. In Nigeria and across Africa that includes many public-sector portals, university websites and news platforms, often looked after by small agencies or a single contractor.
The advisory lists these versions as affected:
- All Drupal 10 releases before 10.6.22
- Drupal 11.0.0 up to (but not including) 11.3.22
- Drupal 11.4.0 up to (but not including) 11.4.13
Old versions get no fix
Drupal 11.2.x and earlier 11 branches, Drupal 10.5.x and earlier, and all of Drupal 8 and 9 are end-of-life and receive no security coverage. If your site runs one of these, there is no patch coming for it; the safe path is to upgrade to a supported branch, and to lock down the installer in the meantime.
Why it matters
A website takeover is not only embarrassing. Attackers who control a site can deface it, plant phishing pages under your trusted domain, inject malicious scripts that target your visitors, steal form submissions and, through code execution, use the server as a foothold into the rest of your network. The US Cybersecurity and Infrastructure Security Agency has flagged five Drupal vulnerabilities as exploited in the wild since November 2021, two of them in ransomware attacks, according to BleepingComputer.
This year has already been busy for Drupal defenders. In May the project confirmed attacks on an SQL injection flaw in its database layer, and more recently it warned that a critical access bypass in the Commerce Core module was being abused.
How to fix it
- Find your version. In the Drupal admin area go to Reports > Status report, or ask your developer or hosting provider.
- Update core. On Drupal 11.4.x move to 11.4.13; on 11.3.x move to 11.3.22; on 10.6.x move to 10.6.22. Take a full backup of files and database first, and test on a staging copy if you have one.
- Secure the installer. The Drupal team recommends securing the installer after installation in any case. If you cannot update right away, block access to /core/install.php in your web server configuration or in the .htaccess file in the web root.
- Check file permissions. The advisory notes that some exploit paths are blocked when the web server cannot write to or change permissions on settings.php. Make sure that file is read-only for the web server user.
- Look for signs of compromise. Because attacks began before many sites patched, review web server logs for requests to install.php since 18 November, check for unfamiliar admin accounts, new or changed files, and unexpected content.
Using Drupal Steward?
Sites protected by the paid Drupal Steward web application firewall service are already shielded from known attack methods, the advisory says. You should still update soon, in case new attack routes are found.
What you should do
- Site owners: ask your developer or hosting provider today, in writing, which Drupal version you run and when it will be updated. Do not assume it happens automatically.
- Developers and agencies: patch every client site you manage, starting with internet-facing and high-traffic ones, then block /core/install.php as a second layer.
- Anyone on Drupal 7, 8, 9 or an unsupported 10/11 branch: plan an upgrade now. Unsupported software will keep collecting unfixed flaws like this one.
- If you find evidence of a break-in, take the site offline or into maintenance mode, restore from a clean backup, change all admin and database passwords, and report the incident to ngCERT or your national CERT.
Sources
- Drupal core – Highly critical – Remote code execution – SA-CORE-2026-017
- BleepingComputer: Drupal patches critical RCE flaw, warns exploits may surface quickly
Featured image: Photo: “Programmer at work (Unsplash)” by Crew, CC0, via Wikimedia Commons — source
Was this article helpful?
adminVerified expert
Cybersecurity Analyst
Federal Capital Territory (Abuja)
Credentials: MCPN, MNCS, IAENG | System Analyst · Web Developer · CEH · CC · CDST
Got expertise to share? Write for us →


