Unrated

Open Redirect and OAuth Token Leakage in Authorizer /authorize Endpoint

IdentifiersCVE-2026-54072CWE-601

CVE-2026-54072 is an open redirect vulnerability in the Authorizer /authorize endpoint. The endpoint accepts attacker-controlled redirect_uri values without applying the same origin validation used elsewhere, allowing an attacker to supply an arbitrary redirection target during the OAuth2 authorization flow. When a victim who is already authenticated is induced to visit a crafted authorization request, the server can issue a 302 redirect to the attacker-controlled destination while including OAuth tokens in the redirect. This can expose access tokens, ID tokens, and refresh tokens to the attacker. The issue affects the authorization flow logic rather than requiring prior authentication by the attacker.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to steal OAuth2 tokens belonging to a logged-in victim by abusing the authorization redirect flow. Exposure of access tokens and ID tokens can enable account impersonation and unauthorized access to protected resources, while exposure of refresh tokens can allow longer-lived session abuse by obtaining new access tokens. The practical impact is full compromise of the victim's authenticated session for as long as the stolen tokens remain valid or renewable.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed version is deployed, reduce or disable exposure of the vulnerable /authorize flow where operationally feasible. Avoid authorization flows that return tokens directly through browser redirects, particularly response types that place tokens into redirect responses such as token or id_token in query-mode redirects. Enforce strict redirect_uri allowlisting at the application, gateway, or reverse-proxy layer, and monitor for suspicious authorization requests containing untrusted redirect targets.

Remediation

Patch, then assume compromise.

Upgrade Authorizer to version 0.0.0-20260409051328-bd3f5baf6d3d or later. The vulnerable /authorize handler should validate redirect_uri using the same origin-validation logic already applied to other handlers in v2.0.1, specifically enforcing strict checks against the configured allowed origins or authorized redirect destinations. After upgrading, review OAuth client configuration to ensure only explicitly trusted redirect targets are permitted.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1