Drupal security updates, in plain English · Module

OpenID Connect Client

329 sites report using it · on drupal.org · 1 security update explained here

This module lets users log in using external authentication services.

Below is every security update for OpenID Connect Client that this site has covered, newest first. Each one says who could exploit it, whether it applies to your site, how urgent it is, and what to tell your developer. If your site uses this module and you are not sure which version, that is the first question to ask whoever looks after it.

OpenID Connect Client

Moderately critical · 329 sites report using it · SA-CONTRIB-2026-287 · on drupal.org · Week of 28 October 2026

The module tries to link a new external login to an existing account with the same email address. Someone could take over an existing account and change or add data. They could not take over the main administrator account.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youThe site is set up to use an external login service that does not verify the email address of the user.
  • 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 OpenID Connect Client to 2.3.1.

For developers: what the fix changed

The fix adds a `link_existing_account` setting (defaulting to false) checked in `OpenidConnectController::authenticate()` and introduces an `isEmailVerified()` check in `LinkExistingAccountSubscriber::linkAccountByEmail()` and `UpdateUserSubscriber::onUserUpdate()` to prevent unverified emails from taking over existing accounts.

Also in this release The release also fixes login redirects not preserving query parameters, fixes unwanted redirects on non-HTML requests, adds typehints, updates development dependencies, and modifies DDEV configurations.

2.3.0 to 2.3.1 16 commits, 25 files.

  • .ddev/config.yaml +1 −1
  • .ddev/docker-compose.keycloak.yaml +5 −7
  • .ddev/docker-compose.web.yaml +4 −4
  • .ddev/githooks/commit-msg +8 −12
  • .ddev/githooks/pre-commit +21 −9
  • .ddev/keycloak/clients/drupal.json +61 −0
  • .ddev/keycloak/realms/oidc.json +0 −0
  • .gitattributes +5 −0
  • .gitignore +0 −1
  • CHANGELOG.md +13 −0
  • composer.json +16 −13
  • config/install/oidc.settings.yml +1 −0 fix

Full diff, 2.3.0 to 2.3.1

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


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 membership bodies, charities 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.