CVE-2026-116672

Authlib RFC 7592 examples omit registration-access-token client binding

Published Oct 27, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
Authlib is a Python library which builds OAuth and OpenID Connect servers. From 0.15 until 1.9.1, the documented ClientConfigurationEndpoint.authenticate_client and ClientConfigurationEndpoint.check_permission reference implementations look up a target client from request-controlled client_id data and check only whether that target is editable, without verifying that request.credential belongs to the target client. Deployments following both examples can allow a client holding any valid registration access token to read, modify, or delete another client's registration. Changing redirect_uris can enable authorization code or token interception, while deleting registrations can deny service to affected clients. This issue is fixed in version 1.9.1.

Analysis

AI-generated

Technical impact

Authlib, a Python library that implements OAuth and OpenID Connect servers, contains reference implementations for the ClientConfigurationEndpoint used during client registration. From version 0.15 through 1.9.1 these implementations look up a target client based on the client_id supplied in the request and verify only that the target is editable, without ensuring that the registration access token presented (request.credential) actually belongs to that client. Consequently, a client holding any valid registration access token can read, modify, or delete another client’s registration data, potentially altering redirect_uris to intercept authorization codes or tokens and even denying service by removing registrations.

Affected Systems

This issue affects any deployment that incorporates Authlib library versions from 0.15 up to and including 1.9.1 and that utilizes the example ClientConfigurationEndpoint.authenticate_client or check_permission code. The vulnerability is tied to the authlib:authlib product, specifically when the sample client‑registration logic is used without additional binding checks.

Risk and Exploitability

With a CVSS score of 8.8 the vulnerability is classified as high severity. EPSS information is not available, and the vulnerability is not listed in CISA’s KEV catalog, but the lack of proper client binding creates a direct path for an attacker who controls a registration access token to impersonate another client. Successful exploitation requires only that the attacker possess a registration access token, which may be obtained through legitimate registration flow or compromised credentials.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Authlib to version 1.9.1 or later to apply the fix.
  • If your deployment uses custom code based on the client‑configuration examples, modify the client lookup logic so that it verifies the credential supplied in the request matches the target client’s registration access token.
  • Re‑validate all OAuth and OpenID Connect client registration endpoints to confirm that client binding and authorization checks are correctly implemented.

Generated by OpenCVE AI on October 27, 2026 at 18:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-c73q-w75p-j82v Authlib RFC 7592 examples omit registration-access-token client binding
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Authlib
Authlib authlib
Vendors & Products Authlib
Authlib authlib
Type Values Removed Values Added
Description Authlib is a Python library which builds OAuth and OpenID Connect servers. From 0.15 until 1.9.1, the documented ClientConfigurationEndpoint.authenticate_client and ClientConfigurationEndpoint.check_permission reference implementations look up a target client from request-controlled client_id data and check only whether that target is editable, without verifying that request.credential belongs to the target client. Deployments following both examples can allow a client holding any valid registration access token to read, modify, or delete another client's registration. Changing redirect_uris can enable authorization code or token interception, while deleting registrations can deny service to affected clients. This issue is fixed in version 1.9.1.
Title Authlib RFC 7592 examples omit registration-access-token client binding
Weaknesses CWE-1188
CWE-639
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 8:15 PM
Reserved
Oct 26, 2026, 8:00 PM
Status
Awaiting Analysis
Published
Oct 27, 2026, 5:16 PM
Modified
Oct 30, 2026, 9:16 PM
Severity
Important
Public date
Oct 27, 2026, 4:31 PM