Drupal 11.4, 11.3 and 10.6 get critical core fix on November 18
The Drupal Security Team announced on November 16 that it will ship a core security release for every supported branch on Wednesday, November 18, 2026, between 17:00 and 21:00 UTC. That is noon to 4:00 p.m. Eastern. The team rates the issues critical, 18 out of 25 on its risk scale, and says at least one can be exploited by an anonymous visitor. CVE numbers and technical details will stay private until the release.
Contents of PSA-2026-11-16
The announcement covers Drupal 11.4.x, 11.3.x and 10.6.x, plus the 12.0.0-beta3 and 11.5.0-beta1 pre-releases. The risk score indicates that more than one site configuration is affected and that proof-of-concept code exists. The team expects working exploits within hours or days of the release and tells site owners not to assume they are safe.
Sites protected by Drupal Steward, the web application firewall service run by the Drupal Association and Security Team, are already filtered against the known attack vectors for this issue. The PSA says other advisories may ship the same day without Steward coverage, so Steward customers still need to update.
Supported branches and end-of-life cutoffs
The current patch releases, published November 6, are 11.4.12, 11.3.21 and 10.6.21. They contain no new core security fixes, but they pull in Symfony and masterminds/html5 updates for upstream advisories. The PSA asks sites to get onto the latest patch release before Wednesday so that any unrelated upgrade problems are found and fixed ahead of time, leaving only the security update for the release window.
Any site older than 10.6.x, and any Drupal 11 site older than 11.3.x, is end of life and will not get a release. For those sites the advisory will include interim mitigation steps, and the permanent fix is an upgrade. Two more deadlines are close. Drupal 10 and Drupal 11.3 both lose security support in December 2026, and the 11.4 branch now ends on April 21, 2027, two months earlier than first planned. The team cut minor-version security coverage from 12 months to 8 on November 2, citing a rise in AI-assisted vulnerability reports that it says exceeds its capacity at current funding levels.
Exploitation timelines for 2026 Drupal core advisories
SA-CORE-2026-004 (CVE-2026-9082), an anonymous SQL injection on PostgreSQL-backed sites, was published May 20. On May 22 the team updated the advisory to report exploit attempts in the wild and raised its risk score, which now stands at 23 of 25. On October 14, SA-CORE-2026-014 (CVE-2026-108097) fixed remote code execution in the Field UI module that some contributed modules expose to unauthenticated users. In 2014, after SA-CORE-2014-005, the team told owners of sites not patched within seven hours to assume compromise. Plan to finish Wednesday's update the same afternoon it ships.
Updating a Composer-managed site to the current patch release
Check the running version:
drush status --field=drupal-version
composer show drupal/core | grep versions
Take a database dump and a copy of the codebase and the sites/default/files directory. Then update core and its pinned dependencies together, run database updates, and rebuild caches:
mkdir -p $HOME/backups
drush sql:dump --gzip --result-file=$HOME/backups/drupal-$(date +%F).sql
composer update "drupal/core-*" --with-all-dependencies
drush updatedb -y
drush cache:rebuild
If Composer will not move to the expected version, run composer why-not drupal/core 11.4.12 (substitute your branch's version) to find the blocking constraint. The usual causes are a contributed module that caps core at an older release, or a composer.json that requires drupal/core with a tight version constraint instead of drupal/core-recommended. Resolve that before Wednesday. Run composer audit afterward to list any other installed packages with published advisories.
Sites installed from a tarball without Composer have to replace the core and vendor directories by hand. Rehearse that on a staging copy now, since it is slower and easier to get wrong under time pressure.
Applying the November 18 release
- Reserve the 17:00 to 21:00 UTC window for whoever does the work, and confirm they have SSH and Composer access to production beforehand.
- Watch drupal.org/security or the security RSS feed for the advisory. Drupal security releases use ordinary version numbers with no marker, so confirm in the advisory which version fixes your branch.
- Run the same
composer update,drush updatedbanddrush cache:rebuildsequence, then load the home page, log in as an editor, and submit a form. - Purge Varnish or CDN caches after the update so visitors are not served pages built by the old code.
- On end-of-life sites, apply the advisory's interim mitigations the same day and check web server logs for requests that match the attack pattern it describes.