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.
CVE-2026-54072
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(medium)
- EG Risk
- 58(Track*)EG Risk 58/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity93% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
September 15, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URL · Advisory · authorizerdev/authorizer · GitHub
https://github.com/authorizerdev/authorizer/security/advisories/GHSA-h29v-hj44-q8cvVendor Advisories for CVE-2026-54072(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/authorizerdev/authorizer | — | 0.0.0-20260409051328-bd3f5baf6d3d | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:18 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 17:34 UTCEG score recompute
- 2026-09-15 16:43 UTCEG score recompute
- 2026-09-13 23:39 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 08:11 UTCEG score recompute
- 2026-09-11 19:36 UTCEG score recompute
- 2026-07-30 12:40 UTCEG score recompute
- 2026-07-26 12:09 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-10 20:12 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-601
Frequently asked(5)
What is CVE-2026-54072?
When was CVE-2026-54072 disclosed?
Is CVE-2026-54072 actively exploited?
What is the CVSS score of CVE-2026-54072?
How do I remediate CVE-2026-54072?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54072
Is Your Infrastructure Affected by CVE-2026-54072?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.