Drupal PSA Security
Upcoming critical Drupal core releases on November 18, 2026 - PSA-2026-11-16
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 informationThis 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 versionsAll 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 policyNeither 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-team channel 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.
Coordinated By:- 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
Security support for Drupal core minor versions reduced to 8 months - PSA-2026-11-02
Drupal has supported each minor release of Drupal (example: 11.3, 11.4) for 12 months each since the release of Drupal 8.6 in 2018.
Like all open source projects, Drupal is enduring a "tsunami" of security reports due to the prevalence of AI tools, and this has created more work than the Drupal Security Team, especially with its current levels of funding, can sustain. For site owners, this introduces risks that security fixes will take longer to release, which gives more time for malicious actors armed with LLMs to find attacks.
The Drupal Security Team and Drupal core release managers explored several options, and ultimately landed on a compromise that brings other benefits such as better alignment with Symfony upstream releases. We will continue protecting Drupal sites for at least 4 years on each major version, while cutting backport work for core security advisories by 30%.
Drupal minor versions will receive 8 months of security coverageBeginning in 2027, Drupal minor versions will receive 8 months of overlapping security coverage (rather than 12 months). This will apply to all versions supported in 2027, meaning that:
- Drupal 11.3 (released December 2025) will still be supported until December 2026.
- Drupal 11.4 (released June 2026) will be supported until April 2027 while the old schedule is being phased out.
- Drupal 12.0 and 11.5 (scheduled for December 2026) will be supported until August 2027.
- Drupal 12.1 and 11.6 (scheduled for June 2027) will be supported until February 2028.
Each minor version will have six months of bugfix support followed by two months of security-only support. The final minor version for each major receives six months of bugfix support followed by six months of security support.
Major versions are still supported for at least 4 yearsWhile the duration of overlapping support for individual minor versions will be reduced, major versions of Drupal core will still be supported for at least four years. This means that:
- Drupal 10 will still be supported until December 2026.
- Drupal 11 (released August 2024) will still be supported until December 2028.
- Drupal 12 (scheduled for December 2026) will be supported until December 2030.
- Benji Fisher (benjifisher) of the Drupal Security Team
- catch (catch) of the Drupal Security Team
- Gábor Hojtsy (gábor hojtsy)
- Greg Knaddison (greggles) of the Drupal Security Team
- Lee Rowlands (larowlan) of the Drupal Security Team
- Dave Long (longwave) of the Drupal Security Team
- James Gilliland (neclimdul) of the Drupal Security Team
- quietone (quietone)
- Angie Byron (webchick) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
- Cathy Theys (yesct) of the Drupal Security Team
Critical PHP update on Wednesday, October 21, 2026 (14:00 UTC) - PSA-2026-10-20
PHP has announced a critical PHP security release for Wednesday, October 21, 2026, at 14:00 UTC. Reserve time to update PHP as soon as the release is available. If you manage PHP yourself, you’ll need to apply the update. If your host manages it, follow their communications for timing and any required action.
Updating to a PHP release containing the patch to these vulnerabilities is the only complete mitigation.
Site owners are responsible for maintaining the security of their hosting platformIt is the policy of the Drupal Security Team that site owners are responsible for monitoring and maintaining the security of third-party libraries and any non-Drupal components of the application and hosting platform. In rare cases, the Drupal Security Team will post an informational public service announcement (PSA) such as this one, but the remit of the Drupal Security Team remains limited to code hosted on Drupal.org’s systems. Previous PSAs on third-party code in the Drupal ecosystem include:
- External libraries and plugins - PSA-2011-002
- Various Third-Party Vulnerabilities - PSA-2019-09-04
- Third-Party Libraries and Supply Chains - PSA-2024-06-26
- Third-Party Libraries and Supply Chains - PSA-2025-09-17
This post is likely to be updated as the situation evolves and more information is available.
Coordinated By:- Greg Knaddison (greggles) of the Drupal Security Team
- Lee Rowlands (larowlan) of the Drupal Security Team
- James Gilliland (neclimdul) of the Drupal Security Team
- Angie Byron (webchick) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
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 versionsAll 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 policyNeither 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-team channel 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
Upcoming critical contributed project security release on September 23, 2026 - PSA-2026-09-21
- Updated 2026-09-22, 12:00 UTC, to document that the advisories in the release might be possible for more common configurations, and that other projects may have advisories.
- Updated 2026-09-21, 19:00 UTC, to document that this is not covered by Drupal Steward.
There will be a security release for a widely used contributed module on September 23, 2026 between 17:00 and 21:00 UTC.
We are announcing this release in advance because the affected contributed module is used on a significant portion of Drupal sites, and the upcoming release will include a significant number of advisories.
The advisory with the highest risk score for the release is currently rated as critical. Other, less severe advisories in the release may be accessible to anonymous users, or result from default configurations.
Other contributed projects may also release advisories on the same date, possibly with more severe vulnerabilities. Drupal core is not affected.
Drupal Steward informationThese releases will not be covered by Drupal Steward.
Advisories may be published in batches (a few at a time)The current rate of advisories may require changes to our practices going forward:
- The security team may publish advisories individually, at different times inside the window.
- We will try to publish batches grouped by module.
- We will announce in Slack when all planned releases for the day are complete.
- We will release mailing list emails about the security updates together at the end of the window, to reduce the risk of site owners updating multiple times while advisories are still being published.
These changes are intended to make the process easier for the team and to make communication from the team easier to follow.
No special release proceduresThe planned update does not require special release procedures.
Solution:Update, 2026-09-23 18:30 UTC: The Webform project has released the below 20 advisories today. Make note of the critical advisory SA-CONTRIB-2026-175, which has slightly increased severity than was originally noted in this public service announcement.
Other advisories than those below were published for other projects, so site owners should follow all normal update procedures.
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-154
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-155
- (Advisory numbers 156 and 157 were accidentally skipped in how we applied the numbering; these are not missing security advisories.)
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-158
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-159
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-160
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-161
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-162
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-163
- Webform - Moderately critical - Access bypass, Server-side request forgery - SA-CONTRIB-2026-164
- Webform - Less critical - Access bypass - SA-CONTRIB-2026-165
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-166
- Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-167
- Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-168
- Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-169
- Webform - Less critical - Denial of service - SA-CONTRIB-2026-170
- Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-171
- Webform - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-172
- Webform - Less critical - Access bypass - SA-CONTRIB-2026-173
- Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-174
- Webform - Critical - Remote Code Execution - SA-CONTRIB-2026-175
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Damien McKenna (damienmckenna) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Dave Long (longwave) of the Drupal Security Team
- Moshe Weitzman (moshe weitzman) of the Drupal Security Team
- Pierre Rudloff (prudloff) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team

Neue Kommentare
vor 2 Wochen 5 Tagen
vor 2 Wochen 5 Tagen
vor 2 Wochen 5 Tagen
vor 3 Wochen 11 Stunden
vor 3 Wochen 14 Stunden
vor 8 Wochen 5 Tagen
vor 9 Wochen 1 Tag
vor 9 Wochen 3 Tagen
vor 9 Wochen 5 Tagen
vor 9 Wochen 5 Tagen