CVE-2026-118554: Oidc · The module enables authentication via the OpenID Connect (oAuth2) protocol
Affects drupal/oidcSource GCVE Database
Not known to be exploited : upgrade to 2.3.1 soon.
Data as of 28 Oct 2026, 20:30 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.3.1
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade drupal/oidc to 2.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/oidc | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the Drupal OIDC module to version 2.3.1 or later, where this vulnerability is fixed. Additionally, ensure that the OpenID Connect provider used verifies the email address of users to mitigate the risk of account takeover.
Description
The Drupal OIDC module allows authentication via the OpenID Connect protocol. A vulnerability exists where an attacker can take over any existing Drupal account (except user 1) that has not yet been linked to an OpenID Connect user by logging in with the same email address. This issue is mitigated if the OpenID Connect provider verifies the user's email address. The vulnerability affects versions prior to 2.3.1 and has been fixed in version 2.3.1.