Skip to main content
← All vulnerabilities
CVE-2026-116672EUVD-2026-111112GHSA-C73Q-W75P-J82V

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 1.9.1
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Authlib, a Python library for building OAuth and OpenID Connect servers, is affected, specifically deployments that follow its documented RFC 7592 client configuration examples. An attacker holding any valid registration access token could read, change, or delete a different client's registration, which could enable interception of authorization codes or tokens or deny service to affected clients.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • authlib authlib

    From 0.15 · fixed in 1.9.1

References 3

GitHub · authlib/authlib