Authorizer: Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URL (CVE-2026-54072) | HOL Guard CVE

Critical severityCVE-2026-54072GHSA-H29V-HJ44-Q8CV

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

Answer in brief

CVE-2026-54072 records a Critical severity vulnerability in Authorizer: Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URL. The current sources do not mark it as known exploited. The current feed maps authorizerdev/authorizer (generic), github.com/authorizerdev/authorizer (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 11, 2026Updated Sep 15, 2026Source checked Sep 17, 2026First seen by HOL Jul 10, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: Critical
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps authorizerdev/authorizer (generic), github.com/authorizerdev/authorizer (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
authorizerdev/authorizergeneric	< 2.2.1	Not reported
github.com/authorizerdev/authorizergo	<0.0.0-20260409051328-bd3f5baf6d3d	0.0.0-20260409051328-bd3f5baf6d3d

Recommended response

Check inventory. Check lockfiles and deployed manifests for authorizerdev/authorizer, github.com/authorizerdev/authorizer.
Review the reported fix. Update github.com/authorizerdev/authorizer to 0.0.0-20260409051328-bd3f5baf6d3d if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 10, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.