(CVE-2026-114542)

Vulnerability from drupal – Published: 2026-10-21 17:54 – Updated: 2026-10-22 21:34 – Source website
VLAI
Details

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.

Since version 6.1.0, the module could cache a token's permissions in a way that let them be reused for another user's token with the same scopes. A user could gain permissions they do not have, including administrative access.

This vulnerability is mitigated by the fact that an attacker needs an OAuth2 token, and cannot trigger the issue themselves: a more privileged user's token with the same scopes must be used first. User 1 is not affected unless security.enable_super_user is set to false.

Credits
Alexander Varwijk (kingdutch) www.drupal.org/u/kingdutch
Jonathan Shaw (jonathanshaw) www.drupal.org/u/jonathanshaw
Mingsong (mingsong) www.drupal.org/u/mingsong
Stephan Huber (stmh) www.drupal.org/u/stmh
Trevor Bradley (trevorbradley) www.drupal.org/u/trevorbradley
References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003e=6.1.0 \u003c6.1.3"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/simple_oauth"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003e=6.1.0 \u003c6.1.3"
          },
          "events": [
            {
              "introduced": "6.1.0"
            },
            {
              "fixed": "6.1.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [
    "CVE-2026-114542"
  ],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/kingdutch"
      ],
      "name": "Alexander Varwijk (kingdutch)"
    },
    {
      "contact": [
        "https://www.drupal.org/u/jonathanshaw"
      ],
      "name": "Jonathan Shaw (jonathanshaw)"
    },
    {
      "contact": [
        "https://www.drupal.org/u/mingsong"
      ],
      "name": "Mingsong  (mingsong)"
    },
    {
      "contact": [
        "https://www.drupal.org/u/stmh"
      ],
      "name": "Stephan Huber (stmh)"
    },
    {
      "contact": [
        "https://www.drupal.org/u/trevorbradley"
      ],
      "name": "Trevor Bradley (trevorbradley)"
    }
  ],
  "details": "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.\n\nSince version 6.1.0, the module could cache a token\u0027s permissions in a way that let them be reused for another user\u0027s token with the same scopes. A user could gain permissions they do not have, including administrative access.\n\nThis vulnerability is mitigated by the fact that an attacker needs an OAuth2 token, and cannot trigger the issue themselves: a more privileged user\u0027s token with the same scopes must be used first. User 1 is not affected unless security.enable\\_super\\_user is set to false.",
  "id": "DRUPAL-CONTRIB-2026-242",
  "modified": "2026-10-22T21:34:41.000Z",
  "published": "2026-10-21T17:54:41.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2026-242"
    }
  ],
  "schema_version": "1.7.0"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.