Live › vulnerability › CVE-2026-114620
Go to dashboardAuthlib's RFC 9101 request-object handling passes the client-supplied request_uri to the application's get_request_object() hook before any destination policy is checked. If the integrator's hook performs an unrestricted outbound fetch, a remote attacker who knows a valid public client ID can make the authorization server request internal or link-local URLs and learn fetch outcomes from error responses and timing.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only deployments that use Authlib as an OAuth or OpenID Connect authorization server with RFC 9101 JWT-secured authorization requests enabled, and whose custom get_request_object hook fetches request_uri without restrictions. Deployments whose hook already applies a secure allowlist, destination controls, and retrieval limits are not affected.
No product ranges from the sources yet.
pip show authlib and confirm whether it is below 1.9.0.get_request_object and check whether it makes outbound HTTP requests without an allowlist, destination controls, and retrieval limits.request_uri parameters.1.9.0 or later.get_request_object hook enforce an allowlist, block internal and link-local destinations, and cap retrieval size and time.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.0, Authlib's RFC 9101 JWTAuthenticationRequest passes the unauthenticated, client-controlled request_uri parameter to the abstract get_request_object() hook before applying a destination or registration policy; the hook itself performs no network request, while the documentation demonstrates an unrestricted HTTP fetch. In deployments whose integrator implements that hook as an unrestricted outbound fetch, a remote attacker who knows a valid public client identifier can make the authorization server request internal, link-local, or otherwise unintended URLs and can distinguish fetch outcomes through different error responses and timing. Deployments whose custom hook already applies a secure allowlist, destination controls, and retrieval limits are not affected. The JWTAuthenticationRequest implementation in authlib/oauth2/rfc9101/authorization_server.py forwards request_uri to get_request_object() before an application-approved retrieval policy accepts the destination. This issue is fixed in version 1.9.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-114620")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.