Skip to content

CVE-2026-54072 Authorizer: Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URL

CriticalCVSS 9.3 EPSS 0.46%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: total

Description

Authorizer is an open-source, self-hostable authentication and authorization server. Prior to version 2.2.1, the /authorize endpoint accepts any redirect_uri without validating it against AllowedOrigins. When response_type=token or response_type=id_token, the server appends access_token, id_token, and refresh_token as query parameters and issues a 302 redirect to the attacker-supplied URL. An unauthenticated attacker can obtain the required client_id from the public /graphql?query={meta{client_id}} endpoint. A partial fix was applied in v2.0.1 to other handlers (oauth_login, verify_email, magic_link_login, forgot_password, invite_members, oauth_callback) but /authorize was not included. Version 2.2.1 contains a more complete fix.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
authorizerdev github.com/authorizerdev/authorizer(Go) < 0.0.0-20260409051328-bd3f5baf6d3d 0.0.0-20260409051328-bd3f5baf6d3d Fixed
authorizerdev github.com/authorizerdev/authorizer = < 2.2.1 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
authorizerdev github.com/authorizerdev/authorizer = < 2.2.1 No fix listed
authorizerdev github.com/authorizerdev/authorizer(Go) < 0.0.0-20260409051328-bd3f5baf6d3d 0.0.0-20260409051328-bd3f5baf6d3d

References