OpenID Connect / OAuth client security updates, in plain English

OpenID Connect / OAuth client

33,019 sites report using it · on drupal.org · 1 security update explained here

This module allows people to log in to the website using an external account provider.

Below is every security update for OpenID Connect / OAuth 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 / OAuth client

Moderately critical · 33,019 sites report using it · 3 security fixes · Week of 4 March 2026

3 security fixes in one update. OpenID Connect / OAuth client fixed 3 separate security bugs this week: 2 access bypass, 1 server side request forgery. One update covers all of them. The most serious, SA-CONTRIB-2026-026, is explained here and the full list is at the end of the card.

A person who is blocked from logging in due to a server error might stay logged in at the external provider. Someone else using the same shared computer could then access the website as that person and see their private information. They could not change any information 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 moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate OpenID Connect / OAuth client to 8.x-1.5.

For developers: what the fix changed

This release carries 3 security fixes. The summary below is for SA-CONTRIB-2026-026, the most serious of them.

The fix adds support for the `prompt` parameter in OpenID Connect authentication requests, defaulting to `login` in `src/Plugin/OpenIDConnectClientBase.php` to ensure users are explicitly prompted to authenticate by the Identity Provider. It also adds an update hook and requirements check in `openid_connect.install` to warn administrators if the prompt is misconfigured.

Also in this release The release also adds entity validation during user creation, improves profile picture handling, fixes a fatal error in the user login form, and adds a GitLab CI configuration and project logo.

8.x-1.4 to 8.x-1.5 6 commits, 8 files.

.gitlab-ci.yml +60 −0
config/schema/openid_connect.schema.yml +36 −0 fix
logo.png +0 −0
openid_connect.install +51 −0 fix
openid_connect.module +7 −4
openid_connect.services.yml +1 −1
src/OpenIDConnect.php +170 −17
src/Plugin/OpenIDConnectClientBase.php +31 −1 fix

Full diff, 8.x-1.4 to 8.x-1.5

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

All 3 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

Moderately critical · Access bypass · SA-CONTRIB-2026-026
Moderately critical · Server side request forgery, Information disclosure · SA-CONTRIB-2026-025
Less critical · Access bypass · SA-CONTRIB-2026-027

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.

OpenID Connect / OAuth client

OpenID Connect / OAuth client

Send me your Drupal site's address.

Get in touch

Links

Reference