Skip to main content
VulnerabilityPublished

CVE-2026-118572: Oauth login oauth2 · This module enables you to log in to your Drupal site using any OAuth 2.0 or

Affects drupal/oauth_login_oauth2Source GCVE Database

0

Not known to be exploited : upgrade to 3.1.1 soon.

Data as of 28 Oct 2026, 20:31 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 3.1.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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/oauth_login_oauth2 to 3.1.1.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/oauth_login_oauth2Affected
  • <3.1.1
Fixed in
  • 3.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the OAuth login OAuth2 module to version 3.1.1 or later, where this vulnerability is fixed. Applying this official fix fully mitigates the issue.

Description

The OAuth login OAuth2 module for Drupal allows login via OAuth 2.0 or OpenID Connect identity providers. A vulnerability exists due to insufficient access checks on a configuration route and lack of verification that the identity provider has confirmed the email address it returns. This flaw enables an attacker to log in as any existing user if they know that user's email address. Exploitation requires the attacker to have an account with a configured identity provider and control over at least one returned attribute, such as username. The issue is fixed in version 3.1.1.

References

Community reviews

Loading reviews…