Drupal's critical core release lands Nov 18
On Monday the Drupal Security Team published PSA-2026-11-16: every supported branch gets a security release on November 18, between 17:00 and 21:00 UTC. It is scored Critical, 18/25. I rarely rewrite my week for a pre-announcement, but this one has two details that change how I plan: a proof of concept already exists, and at least one of the issues is reachable by anonymous users.
What the PSA actually says
The vector is AC:Complex, A:None, CI:All, II:All, E:Proof, TD:Uncommon. In plain terms: exploitation is not trivial, it needs no authentication, it could expose or modify all data, and it only applies to uncommon module configurations. The team also states that more than one configuration is affected and that exploits might appear within hours or days of the release.
What it does not say is the vulnerability type. Details are withheld until the advisory, so anything you read today that claims to know the mechanism is guessing. I'm not going to guess either.
Which versions are in scope
- Drupal 11.4.x, 11.3.x and 10.6.x receive security releases.
- 12.0.0-beta3 and 11.5.0-beta1 are affected too, and new beta builds will follow.
- Anything older than 10.6.x, and Drupal 11 before 11.3.x, is unsupported and affected, with no official patch. The team says interim mitigation steps will come with the advisory.
That last bullet is where the shortened minor-version support window bites. If you are on 11.2 or earlier, tomorrow you get instructions instead of a fix.
What I'm doing before the window opens
The PSA's most practical advice is to update to the latest patch release of your current branch before November 18, so the security update is a small diff and not a surprise migration. I'm following it:
- Check where each site stands with
composer show drupal/coreand bring it to the newest patch on its branch today. - Confirm a restorable backup exists. A green dashboard is not proof, so I restore one to a scratch box.
- Block out the afternoon of the 18th. With a public proof of concept, "I'll do it Friday" is a real risk.
- Pin down which sites are unsupported and decide now whether they get mitigations or a rushed upgrade.
Drupal Steward customers are protected from the known attack vectors, but the PSA notes other advisories may ship the same day without Steward coverage, so it is not a reason to skip the update.
One more line from the PSA is worth repeating: don't act on unsolicited emails describing a Drupal core security issue. Pre-announcements attract phishing, and a fake "urgent patch" is an easy way to get a developer to run something nasty.
My take
A pre-announced, anonymous-reachable, proof-of-concept-backed critical is the scenario the PSA process exists for. The details arrive tomorrow; the preparation is today's job. I'll read the actual advisory when it lands, and if it changes the picture I'll write that up properly.