CVE-2026-122058: Composer/drupal/simple_oauth vulnerability

Published Nov 4, 2026
·
Updated

This module introduces an OAuth 2.0 authorization server, which can be configured to protect your Drupal instance with access tokens, or allow clients to request new access tokens and refresh them.

The module doesn't sufficiently restrict access to consumer configuration. Users who can create or edit consumers can potentially configure malicious consumers and obtain tokens with additional privileges. This can allow them to access the site as another user, up to full administrative access.

This vulnerability is mitigated by the fact that an attacker must have a role with the Add consumer entities or Update own consumer entities permissions.

Affected Software

3 affected componentsFixes available
composer/drupal/simple_oauth<5.2.6
5.2.6
composer/drupal/simple_oauth>=6.0.0<6.0.10
6.0.10
composer/drupal/simple_oauth>=6.1.0<6.1.4
6.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/simple_oauth to a version that resolves this vulnerability.

    Fixed in 5.2.6
  2. Upgrade

    Upgrade composer/drupal/simple_oauth to a version that resolves this vulnerability.

    Fixed in 6.0.10
  3. Upgrade

    Upgrade composer/drupal/simple_oauth to a version that resolves this vulnerability.

    Fixed in 6.1.4

Event History

Nov 4, 2026
Advisory Published
via OSV·05:31 PM
Data Sourced
via OSV·05:31 PM
DescriptionAffected Software

Frequently Asked Questions

1

Who is realistically able to exploit this issue?

An attacker must hold a role with either the Add consumer entities permission or the Update own consumer entities permission. Users without either permission are not identified as able to exploit the issue.

2

What level of access could an attacker obtain?

A permitted attacker may configure a malicious consumer to obtain tokens with additional privileges and access the site as another user. The potential impact extends up to full administrative access.

3

What should be reviewed while remediation is pending?

Review which roles have the Add consumer entities and Update own consumer entities permissions, and remove those permissions from untrusted users where possible. Review consumer configurations created or edited by users with those permissions for malicious settings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203