12 Oct 2026
Drupal.org aggregator
Droptica: Drupal security updates in the AI era: why “we’ll patch next sprint” no longer works
Most Drupal site owners I talk to handle Drupal security updates the same way. These are the fixes the Drupal Security Team publishes for core and contributed modules. A developer sees the security advisory. A ticket goes into the next sprint. The patch goes live a few days later, sometimes two weeks later.
12 Oct 2026 5:45pm GMT
Dynamosys Insights: Playwright for Drupal: A Practical Guide to Test Automation
A Drupal update should come with confidence that your important workflows still work. Learn how to introduce Playwright, build useful browser tests, and make automation part of your release process.
12 Oct 2026 4:43pm GMT
Security public service announcements: Upcoming critical Drupal core release on October 14, 2026 - PSA-2026-10-12
There will be a Drupal core security release for all supported branches on October 14, 2026 between 16:00 and 21:00 UTC. (To see this in your local timezone, refer to the Drupal Core Calendar.) Based on our analysis this vulnerability rates at 19/25 on our risk calculator.
The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.
We recommend updating to the latest supported patch (bugfix) release for your site's version of Drupal before October 14, so that you can address any other upgrade issues before the security window.
This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.
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-beta1 is also affected. New beta releases will be provided following the security updates for the 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 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.)
- Bram Driesen (bramdriesen) of the Drupal Security Team
- catch (catch) of the Drupal Security Team
- Damien McKenna (damienmckenna) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- 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
- Jess (xjm) of the Drupal Security Team
12 Oct 2026 4:10pm GMT