Drupal security updates, week of 4 February 2026: Login Disable

Week of 4 February 2026

Drupal publishes security updates on Wednesdays. This week there was one, for a module.

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.

Login Disable

Less critical · 499 sites report using it · SA-CONTRIB-2026-008 · on drupal.org

This module stops people from logging in to the website unless they know a secret code to add to the web address.

A person with an ordinary account on the site can log in using a specific web address without needing the secret code. They cannot read any extra information. They cannot change anything on the site.

Who could do thisOnly someone with a login on your site.
Does it apply to youAny site using this module.
Has it been used in attacksNo sign of it.
How urgentDrupal rates this less critical. Fix it with the next routine update.

Tell your developerUpdate Login Disable to 2.1.3.

For developers: what the fix changed

The fix adds a route subscriber in `src/EventSubscriber/LoginDisableRouteSubscriber.php` to attach a custom access check to the `user.login.http` route. The access check, implemented in `src/Access/LoginDisableAccessCheck.php`, verifies that the required access key is present in the request URL before allowing login.

Also in this release Added automated tests for the HTTP login functionality.

2.1.2 to 2.1.3 1 commit, 4 files including 1 test.

login_disable.services.yml +13 −0 fix
src/Access/LoginDisableAccessCheck.php +58 −0 fix
src/EventSubscriber/LoginDisableRouteSubscriber.php +23 −0 fix

Full diff, 2.1.2 to 2.1.3

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

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.

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.

Week of 4 February 2026

Less critical: 1 update

Login Disable

Send me your Drupal site's address.

Get in touch

Links

Reference