Drupal CMS · Exploitation reported

[Single source] Drupal patches critical installer flaw allowing site takeover

· 1 min read

Drupal released a fix for CVE-2026-132165, an installer flaw that, under specific conditions, lets an unauthenticated attacker take over the site or run remote code. The advisory reports no active exploitation, and patches cover supported branches: 11.4.13, 11.3.22 and 10.6.22. Update now, secure the installer and migrate installations on unsupported branches.

Illustration: Drupal patches critical installer flaw allowing site takeover
WhatsApp LinkedIn X
HighVulnerabilityExploitation reportedPatched

In 30 seconds

DailyDarkWeb
Observed

Drupal published a critical security advisory today, November 18, and the message is simple: update now. The advisory, SA-CORE-2026-017, ships fixes for CVE-2026-132165, a flaw in the installer, the setup tool that builds a new Drupal site.drupal.orgdrupal.org · rssOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

According to the advisory as summarized publicly, an attacker who has no account on the site could, under specific conditions, abuse that installer to take over the site entirely or achieve remote code execution, which means running commands on the server.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

Supported branches get patches: 11.4.x moves to 11.4.13, 11.3.x to 11.3.22 and 10.6.x to 10.6.22. Older branches have no fix coming and need a supported upgrade path. No active exploitation is reported so far.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

What happened

Observed

The official advisory went live on drupal.org on November 18, 2026, and the first public discussion appeared at the same moment, so this is a fresh, same day disclosure.drupal.orgdrupal.org · rssOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

The problem sits in the installer. Under specific conditions, it can be abused by an unauthenticated attacker, meaning one holding no credentials at all, for site takeover or remote code execution.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

Drupal released patches for the three supported branches and pointed admins on older, unsupported branches to a supported upgrade path, since those versions receive no fix.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

The advisory does not report active exploitation, according to the public summary. Treat that as a snapshot of the moment of release, not a guarantee about tomorrow.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Why it matters

Alleged

Drupal rates this Critical, 18 out of 25 on its own risk scale, which is not the CVSS score many admins expect. Either way the ceiling is high: full site takeover or code execution from an unauthenticated position, the cheapest starting point an attacker can have.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

The installer angle matters because setup tooling is usually treated as harmless plumbing. If a build script can be weaponized, defenses tuned to normal site traffic may simply never look at it.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

Unsupported branches are the soft spot. They get no patch, so every site still running one carries the exposure until it migrates, and the advisory's only answer for them is an upgrade path.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

What to do

Alleged

Update immediately if you run a supported branch: 11.4.x to 11.4.13, 11.3.x to 11.3.22 and 10.6.x to 10.6.22.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

If you are on an unsupported branch, start planning the move to a supported one now. No patch is coming for the old line, so migration is the only fix.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

The advisory also recommends securing the installer itself. Mind the limits: restricting the web server's ability to write or change permissions on settings.php, the file holding the site's core configuration, blunts only some exploit paths.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

Do not lean on Drupal Steward, the project's protection service that filters malicious traffic, as your only shield. It does not cover every possible exploit path.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Confirmed and still uncertain

Observed

What is established: the advisory exists and is dated today, patches cover three branches, the flaw involves installer abuse by unauthenticated attackers under specific conditions, and no active exploitation is reported.drupal.orgdrupal.org · rssOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

What is not yet clear: the public summary does not spell out the specific conditions required for exploitation, no CVSS score has been published, and there is no word on whether anyone has tested the flaw against real sites.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

Also unknown is how fast attackers react. Patched critical flaws in widely used software tend to attract scanning quickly, but that is pattern reading, not evidence about this case.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

What people are saying

Observed

DailyDarkWeb, a security account that tracks vulnerability news, surfaced the advisory and framed it plainly: update supported branches now, and treat older branches as needing a supported upgrade path.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Observed

The same thread cautions against overconfidence in partial fixes, noting that locking down writes to settings.php mitigates only some exploit paths and that Drupal Steward protection does not cover every possibility.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Evolution

Observed

This story is one beat old. The advisory and the first public discussion share the same timestamp of November 18, 2026, so the disclosure itself is the starting point and there is no earlier public history in this batch.drupal.orgdrupal.org · rssOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

The usual sequence from here: admins patch, researchers dig into the diff for exploit details, and proof of concept attempts may follow. None of that has appeared in the evidence yet.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Reach

Observed

1 independent groups, 1 updates, and 1 engagements.

Technical detail

Alleged

The mechanics, as summarized: the installer can be abused by an unauthenticated attacker under specific conditions, leading to site takeover or remote code execution. The public summary does not detail what those conditions are, so the official advisory is the place to check.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

On scoring: Drupal rates the issue Critical at 18 of 25 on its own scale. The account flagging it makes a point worth repeating, that this number is not CVSS, so tooling calibrated to CVSS should not downrank it.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Alleged

On defenses: restricting the web server's ability to write or change permissions on settings.php mitigates some paths, not all, and Drupal Steward, which filters malicious requests, also does not cover every path.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Sources and evidence

Observed

Primary source: the official Drupal security advisory at drupal.org, published November 18, 2026. That page is the authoritative record for affected versions and recommendations.drupal.orgdrupal.org · rssOpen original sourceSee in source list

Observed

Supporting source: a DailyDarkWeb post on X that summarizes the advisory, lists the patched versions, flags the risk scale nuance and attaches a screenshot of the notice.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list

Inferred

Evidence limits: the advisory's full text was not included in this batch, so the technical details here rest on a public summary of it. Check the official page for the definitive wording before acting on specifics.drupal.orgdrupal.org · rssOpen original sourceSee in source list

Sources

  1. drupal.orgdrupal.org · rss
  2. DailyDarkWebx.com · DailyDarkWeb · x

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click