External risk intelligence

Authorizer open redirect vulnerability in /authorize endpoint.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-54072

The vulnerable product is an authentication and authorization server. Such services are designed to be public-facing to handle login, identity, and OAuth workflows for users and applications, making them inherently internet-accessible by design.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in the Authorizer authentication and authorization server could allow unauthenticated attackers to redirect users to malicious sites, potentially leading to compromised credentials or tokens. This issue arises from improper validation of redirect URIs within the `/authorize` endpoint. While a partial fix was previously applied, the affected endpoint remained vulnerable until version 2.2.1. The main concern is confirming relevance and exposure.

  • Open redirect vulnerability in authentication server.
  • Affects user authentication and token handling.
  • Confirm relevance and exposure to your systems.

Attack Path

How an attacker could exploit the issue

An attacker can leverage this vulnerability by first obtaining a valid `client_id` from a publicly accessible endpoint. They can then craft a malicious URL that includes this `client_id` and a specially chosen `redirect_uri`. When a user clicks this malicious link, the vulnerable server will redirect them to the attacker's chosen URL, potentially exposing sensitive tokens.

  • Requires a valid client ID.
  • Triggers via a crafted redirect URL.
  • Risk of sensitive token exposure.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability could allow an unauthenticated attacker to trick users into a redirect, potentially exposing sensitive tokens in the URL.

  • Sensitive tokens could be exposed.
  • Users could be redirected to malicious sites.
  • Token leakage to an attacker.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and platform teams are likely responsible for addressing this vulnerability in the Authorizer service. The first practical step is to identify all deployments of Authorizer, confirm their reachability and business criticality, and then assign ownership for remediation planning.

  • Identify and confirm Authorizer deployments.
  • Verify exposure and business impact.
  • Plan vendor coordination or upgrade.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Authorizer?

Authorizer is an open-source, self-hosted service designed to manage user identity, authentication, and authorization workflows. It acts as a central hub where applications send users to log in or verify their identity using OAuth-style flows. Because it handles sensitive credentials and security tokens, it is a critical component in the identity infrastructure of any application that uses it.

What does CWE-601 mean for CVE-2026-54072?

CWE-601 is the classification for URL Redirection to Untrusted Site, commonly known as an open redirect. In the context of CVE-2026-54072, this means the server fails to verify where it is sending a user after login. Instead of checking if the destination is trusted, it blindly redirects the user to whatever URL is provided in the request, which can be manipulated to send users to a malicious site.

How can an attacker trigger this vulnerability?

An attacker triggers this by crafting a specific URL targeting the /authorize endpoint. They first retrieve a valid client ID from a public metadata endpoint and then inject a malicious redirect URI into the authorization request. Note that simply browsing the server's home page or accessing unrelated endpoints does not trigger the vulnerability; it specifically requires the crafted redirect request during the authentication flow.

Is my Authorizer instance at risk?

According to Halo Surface Signal, this vulnerability is highly relevant because Authorizer is built to handle OAuth workflows, meaning it is almost always deployed as an internet-facing service. If your instance is reachable from the public internet, an attacker can attempt to use it to redirect users and capture sensitive security tokens, making it a priority to check your deployment version.

How do I fix CVE-2026-54072?

The primary response is to update your Authorizer installation to version 2.2.1 or later. This version introduces a comprehensive fix that correctly validates redirect URIs against your configured AllowedOrigins list. Before updating, identify all instances of Authorizer within your environment to ensure that every deployment is patched and that the security fix is applied across your entire authentication infrastructure.

References