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.
Github GHSA