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

Advisory record · `GHSA-h29v-hj44-q8cv`

- **Identifiers:** `GHSA-h29v-hj44-q8cv` · `CVE-2026-54072` · `GO-2026-5959`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-601](https://cwe.mitre.org/data/definitions/601.html)
- **Tags:** [Open redirect](https://agentprime.io/advisories/tag/open-redirect.md)
- **Published:** 10 Jul 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Jul 2026, 19:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/authorizerdev/authorizer` (Go): affected `<0.0.0-20260409051328-bd3f5baf6d3d`; fixed in `0.0.0-20260409051328-bd3f5baf6d3d`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go package github.com/authorizerdev/authorizer is affected in versions before 0.0.0-20260409051328-bd3f5baf6d3d. The /authorize endpoint does not validate the redirect_uri parameter against AllowedOrigins, so when response_type is token or id_token, access, ID, and refresh tokens are sent to an attacker-supplied URL. An attacker who gets a logged-in user to click a crafted link can steal those tokens and impersonate the user; the attacker needs the client_id, which the source says is publicly available. Upgrade to 0.0.0-20260409051328-bd3f5baf6d3d or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h29v-hj44-q8cv)

## Sources

- [GitHub Advisory Database: GHSA-h29v-hj44-q8cv](https://github.com/advisories/GHSA-h29v-hj44-q8cv)
- [OSV: GHSA-h29v-hj44-q8cv](https://osv.dev/vulnerability/GHSA-h29v-hj44-q8cv)
- <https://github.com/authorizerdev/authorizer/security/advisories/GHSA-h29v-hj44-q8cv>
- <https://github.com/authorizerdev/authorizer>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h29v-hj44-q8cv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h29v-hj44-q8cv/>. Everything for agents: <https://agentprime.io/llms.txt>.
