There will be a Drupal core security release for all supported branches on November 18, 2026 between 17:00 and 21:00 UTC. (To see this in your local timezone, refer to the Drupal Core Calendar.)
The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.
The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users. More than one configuration is affected, so do not assume your site is safe.
We also recommend updating to the latest supported patch (bugfix) release for your site's version of Drupal before November 18, so that you can address any other upgrade issues before the security window.
Drupal Steward information
This issue is being mitigated by Drupal Steward. Sites that use Drupal Steward are already protected from known attack vectors. Other security advisories may be released on the same date without Drupal Steward mitigation. Sites should upgrade in the near future to ensure that they are protected from all published advisories.
Affected versions
All currently supported versions of Drupal core are affected, including:
- Drupal 11.4.x
- Drupal 11.3.x
- Drupal 10.6.x
Drupal 12.0.0-beta3 and 11.5.0-beta1 are also affected. New beta or release candidate versions will be provided following the security updates for the currently supported branches.
All versions of Drupal prior to 10.6.x as well as all versions of Drupal 11 prior to 11.3.x are end-of-life and no longer supported. Sites on those versions should apply the interim mitigation steps that will be provided in the upcoming security advisory, and update as soon as possible to avoid this and other publicly disclosed vulnerabilities.
Disclosure policy
Neither the Security Team nor any other party is able to release any more information about this vulnerability until the announcement is made. Security release announcements will appear on the Drupal.org security advisory page, which has RSS feeds. The announcement will also be made public on:
- The
#security-teamchannel of the Drupal community Slack - Bluesky
- Mastodon
- X (formerly Twitter)
- By email for those who have subscribed to our email list. (To subscribe to the email list: log in on Drupal.org, go to your user profile page and subscribe to the security newsletter on the Edit » My newsletters tab.)
If you have received an unsolicited email describing a potential Drupal core security issue, please do not forward it or act on instructions in it.
- Alex Pott (alexpott) of the Drupal Security Team
- Benji Fisher (benjifisher) of the Drupal Security Team
- catch (catch) of the Drupal Security Team
- cilefen (cilefen) of the Drupal Security Team
- David Strauss (david strauss) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Tim Hestenes Lehnen (hestenet)
- Lee Rowlands (larowlan) of the Drupal Security Team
- Dave Long (longwave) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Michael Hess (mlhess) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Pierre Rudloff (prudloff) of the Drupal Security Team
- Angie Byron (webchick) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team