SB2026110612 - Multiple vulnerabilities in Doorkeeper



SB2026110612 - Multiple vulnerabilities in Doorkeeper

Published: November 6, 2026 Updated: November 6, 2026

Security Bulletin ID SB2026110612
CSH Severity
Medium
Patch available
YES
Number of vulnerabilities 2
Exploitation vector Remote access
Highest impact Data manipulation

Breakdown by Severity

Medium 50% Low 50%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 2 vulnerabilities.


1) Improper Authentication (CVE-ID: N/A)

CWE-ID: CWE-287 - Improper Authentication

CVSSv4: 6.3 [CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N]


The vulnerability allows an unauthenticated remote attacker to cause requests to execute under an unintended identity, including a gateway's identity, bypass token-based scope checks across infrastructure layers, and corrupt attribution, rate limiting, and resource-owner resolution.

The vulnerability exists due to Doorkeeper accepting simultaneous access-token transmission through the Authorization Bearer header, form-encoded body, and URI query instead of rejecting the request, selecting the first token yielded by the order in access_token_methods and silently discarding others, prioritizing access_token over bearer_token when both parameters are present, and reading merged body/query parameters that give the query precedence in Rails but the body precedence in Rack/Grape; this affects resources protected by doorkeeper_authorize!, including Rails, Grape, and controllers using Doorkeeper's base classes, as well as GET /oauth/token/info and the bearer-token authorization path of POST /oauth/introspect. An unauthenticated remote attacker can supply competing tokens without privileges beyond possession of the tokens they present, exploiting a gateway that adds its own Bearer header while forwarding a caller-controlled token parameter to execute under the gateway's identity without an error or log entry, or exploiting a WAF, gateway, or middleware that checks a different transmission method to pass a scope check on one token while Doorkeeper executes under another; configured extraction order determines which token wins, body/query collisions resolve differently across frameworks, and a revoked token selected ahead of a valid token causes authentication to fail rather than using the valid token.


2) Improper Authentication (CVE-ID: N/A)

CWE-ID: CWE-287 - Improper Authentication

CVSSv4: 6.3 [CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N]


The vulnerability allows an unauthenticated remote attacker to cause incorrect client attribution for OAuth token issuance, revocation, or introspection under an unintended client identity.

The vulnerability exists due to Doorkeeper's client authentication component in lib/doorkeeper/oauth/client/credentials.rb accepting multiple simultaneous authentication methods instead of rejecting them as required by RFC 6749, with Client::Credentials.from_request returning the first non-blank credentials and silently discarding others without an error, warning, or log entry; the default client_credentials_methods checks HTTP Basic authentication before form parameters for /oauth/token, /oauth/revoke, and /oauth/introspect. An unauthenticated remote attacker can submit requests containing Basic credentials for one client and client_id/client_secret form parameters for another, provided valid credentials are available for at least one presented identity, causing valid Basic credentials to determine the authenticated client even when the body contains another client's complete valid credentials; in gateway or proxy integrations that attach their own Basic credentials while forwarding caller-controlled body credentials, this silently overrides the caller's intended client identity.


Remediation

Install update from vendor's website.