CVE-2026-118669 — OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client

Affected: oauthlib

OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. Prior to 4.0.0, the client_credentials and Resource Owner Password Credentials token grant handlers can authenticate request.client as one confidential client while retaining an attacker-supplied request.client_id for validate_grant_type and validate_scopes. A lower-privilege authenticated client can therefore cause grant and scope authorization to use another client's identity when an application validator relies on the documented client_id argument, potentially issuing tokens with unauthorized grants or scopes. Validators that authorize exclusively from request.client may not be affected. This issue is fixed in version 4.0.0.

GHSA-7984-qgvg-3j9c — OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client

Affected: PyPI: oauthlib

## Summary

OAuthlib's token grant handlers can authenticate one client while authorizing the grant type and requested scopes using a different, attacker-supplied `client_id` from the request body.

In affected token grant flows, `authenticate_client(request)` sets `request.client` to the authenticated client object, but OAuthlib does not require `request.client_id` to match `request.client.client_id`. If the request body already contains `client_id=...`, OAuthlib keeps that value and passes it to `validate_grant_type()` and `validate_scopes()`.

As a result, an authenticated low-privilege confidential client can authenticate as itself, submit another client's `client_id` in the token request body, and cause grant and scope validation to run under that other client identity.

## Affected Surface

The affected public surface is the OAuth2 token endpoint handling for:

- `client_credentials` - `password` / Resource Owner Password Credentials

The issue is relevant to OAuthlib provider deployments where:

- the attacker has credentials for one valid lower-privilege confidential client; - another client has broader grants or scopes; - the application validator uses the `client_id` argument passed by OAuthlib in `validate_grant_type()` or `validate_scopes()`, as the `RequestValidator` API is designed to support.

Deployments whose validators ignore the `client_id` argument and authorize only from `request.client` may not be affected.

## Details

`Request` parses query and body p…

Most recent entries from all

CVE-2026-118669 — OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client

GHSA-7984-qgvg-3j9c — OAuthLib: Token grants can use attacker-supplied client_id for authorization after authenticating a different client