Skip to main content
CVE-2026-118573VulnerabilityPublished

drupal/oauth2_token_manager · Oauth2 token manager: This module lets you manage system-wide OAuth2 access and refresh tokens for Box, Quip, and

Affects drupal/oauth2_token_managerSource GCVE Database

0

Not known to be exploited : upgrade to 1.2.0 when convenient.

Data as of 28 Oct 2026, 20:30 UTC

Severity
Medium

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

Patch
Available – fixed in 1.2.0

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/oauth2_token_manager to 1.2.0.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/oauth2_token_managerAffected
  • <1.2.0
Fixed in
  • 1.2.0

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

AI-suggested

Upgrade the OAuth2 Token Manager module to version 1.2.0 or later, where the vulnerability is fixed. No additional mitigation steps are indicated.

Description

The OAuth2 Token Manager module for Drupal allows management of system-wide OAuth2 access and refresh tokens for integrations such as Box, Quip, and Slack. A vulnerability exists because the module does not restrict access to its OAuth2 routes, potentially allowing an anonymous visitor to connect the site's integration to an account they control. However, exploitation requires the attacker to obtain the OAuth2 state value from a prior token initialization, which mitigates the risk. The issue is fixed in version 1.2.0.

References

Community reviews

Loading reviews…