Drupal security updates, in plain English

Week of 29 July 2026

Drupal publishes security updates on Wednesdays. This week there were 3, all for modules.

None for Drupal core, so nothing here applies to every site.

Each card says what the module does, what went wrong, who could do it, whether it applies to you, how urgent it is, and the one line to send to your developer. Worst rated first, and most used first within a rating.

New here? How Drupal security updates work explains who publishes these, why they matter and what the ratings mean. Earlier weeks and a search by module are on the main page.

Critical: 2 updates

Cyber Essentials expects a fix within 14 days. Do it this week.

Disable Login Page

Critical · 1,613 sites report using it · SA-CONTRIB-2026-091 · on drupal.org

This module stops visitors from seeing the standard login page unless they have a secret key.

This project has been withdrawn because of a security problem its maintainer did not fix. The details are not published. It should be treated as unsafe to keep.

  • Who could do thisOnly someone with an administrator login.
  • Does it apply to youAny site using this module.
  • Has it been used in attacksNo sign of it.
  • How urgentThe Drupal security team has withdrawn this module because its maintainer did not fix a known problem. The only remedy is to remove or replace it.

Tell your developerRemove or replace Disable Login Page. There is no fixed version.

For developers: what the fix changed

The module has been withdrawn, so there is no fixed release to compare.

Powerful Surveys

Critical · no install count published · SA-CONTRIB-2026-092 · on drupal.org

This module provides survey features for a website.

This project has been withdrawn because of a security problem its maintainer did not fix. The details are not published. It should be treated as unsafe to keep.

  • Who could do thisOnly someone with an administrator login.
  • Does it apply to youAny site using this module.
  • Has it been used in attacksNo sign of it.
  • How urgentThe Drupal security team has withdrawn this distribution because its maintainer did not fix a known problem. The only remedy is to remove or replace it.

Tell your developerRemove or replace Powerful Surveys. There is no fixed version.

For developers: what the fix changed

The distribution has been withdrawn, so there is no fixed release to compare.

Moderately critical: 1 update

Include in your next routine update, within the month.

Token Content Access

Moderately critical · 878 sites report using it · SA-CONTRIB-2026-090 · on drupal.org

This module lets website managers grant access to pieces of content using special codes.

Someone could guess the special code by measuring how long the website takes to reply. They could then read hidden pieces of content protected by this module. They could not change any information on the website.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youThis applies if someone knows or finds the web address for the protected piece of content.
  • Has it been used in attacksNo sign of it.
  • How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate Token Content Access to 3.1.2.

For developers: what the fix changed

The fix replaces a standard string comparison with the timing safe hash_equals function in src/Access/TcaAccessCheck.php to prevent timing attacks, and limits the token length in tca.module.

Also in this release The release also refactors tca_form_alter in tca.module to use early returns and improve code readability.

3.1.1 to 3.1.2 2 commits, 2 files.

  • src/Access/TcaAccessCheck.php +4 −4 fix
  • tca.module +33 −18 fix

Full diff, 3.1.1 to 3.1.2

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

Not sure what your site is running?

Send me your Drupal site's address.

I'll tell you what I can see from outside, what the Drupal 10 end of life on 9 December means for it, and what it would cost to have me keep it patched. There's no charge for that and no obligation. peter@peterbrady.co.uk

Compiled 10 October 2026 as part of the archive back to January 2026, from the advisories published by the Drupal security team on drupal.org. The facts on each card are theirs. The plain English is mine, with help from a language model. In the archive the cards rated critical or above were read before publishing and the rest were checked by sampling. Install counts are today's, not the count on the day of the advisory.


Get in touch

Tell me who you are, what your organisation does, and what you need. That might be a Drupal site that needs looking after, an upgrade to get done before December, or an agency that needs Drupal cover.

If I can help, I'll say so and suggest a call. If I can't, I'll tell you straight away rather than waste your time.

peter@peterbrady.co.uk

For context: I work mainly with UK charities, membership bodies and research organisations, and with the agencies that look after their websites. Not recruiters.

Or start smaller and connect with me on LinkedIn. That's where I post what I find digging around in charity and grants data, and where the free tools turn up first.