Vulnerabilities in pkg:golang/github.com/authorizerdev/authorizer
PACKAGECVE-2026-35511 is a HIGH zero-click account takeover vulnerability (CWE-287: Improper Authentication) affecting Authorizer libraries in the Go ecosystem. The issue involves zero-click account takeover via oauth identity linking to unverified email accounts. Remediation is available by upgrading affected packages to version 0.0.0-20260807033110-66fe488fd2a4.
pkg:golang/github.com/authorizerdev/authorizer
Vulnerability advisories affecting package pkg:golang/github.com/authorizerdev/authorizer. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-29rf-f4vv-pvq6 | CVE-2026-35511 | HIGH | Authorizer: Zero-click account takeover via OAuth identity linking to unverified email accounts |
| GHSA-h29v-hj44-q8cv | CVE-2026-54072 | CRITICAL | Authorizer: Unvalidated redirect_uri in /authorize leaks OAuth2 tokens to attacker-controlled URL |
| GHSA-x3f4-v83f-7wp2 | - | HIGH | Authorizer: Password reset token theft and full auth token redirect via unvalidated redirect_uri |
| GHSA-jfwg-rxf3-p7r9 | - | HIGH | Authorizer: CQL/N1QL Injection in Cassandra and Couchbase Backends via fmt.Sprintf String Interpolation |
CVE-2026-35511 at a Glance
How to Fix CVE-2026-35511
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.
Upgrade github.com/authorizerdev/authorizer to 0.0.0-20260807033110-66fe488fd2a4
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 CVE-2026-35511, 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-20260807033110-66fe488fd2a4), 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-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. 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
CVE-2026-35511 Affected Authorizer Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/authorizerdev/authorizer
|
Go |
< 0.0.0-20260807033110-66fe488fd2a4
|
0.0.0-20260807033110-66fe488fd2a4
|
References
Frequently Asked Questions
What is CVE-2026-35511?
Which Authorizer versions are affected?
What version fixes CVE-2026-35511?
Is github.com/authorizerdev/authorizer affected?
What CWE is associated with CVE-2026-35511?
How can I check Go dependencies for CVE-2026-35511?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-29rf-f4vv-pvq6",
"modified" : "2026-08-14T15:36:15Z",
"published" : "2026-08-14T15:36:15Z",
"aliases" : [ "CVE-2026-35511" ],
"summary" : "Authorizer: Zero-click account takeover via OAuth identity linking to unverified email accounts",
"details" : "The OAuth callback handler links incoming OAuth identities (Google, GitHub, etc.) to existing accounts matched by email address without verifying that the existing account's email was verified by its original owner. An attacker who pre-registers with a victim's email address (without verifying it) gains persistent password-based access to the victim's account after the victim completes a normal OAuth login. Verified against HEAD (commit 73679fa).\n\n## Root Cause\n\nIn `internal/http_handlers/oauth_callback.go`, when an OAuth login occurs for an email that already exists in the database:\n\nLine 125: The existing user is looked up by email:\n\n existingUser, err := h.StorageProvider.GetUserByEmail(ctx, refs.StringValue(user.Email))\n\nLine 164: The OAuth user object is replaced with the existing user:\n\n user = existingUser\n\nLines 173-176: The OAuth provider is appended to the existing user's signup methods:\n\n signupMethod := existingUser.SignupMethods\n if !strings.Contains(signupMethod, provider) {\n signupMethod = signupMethod + \",\" + provider\n }\n user.SignupMethods = signupMethod\n\nLines 179-181: If the existing account's email was NOT verified, it is automatically verified:\n\n if user.EmailVerifiedAt == nil {\n now := time.Now().Unix()\n user.EmailVerifiedAt = &now\n }\n\nLine 219: The merged user is saved to the database:\n\n user, err = h.StorageProvider.UpdateUser(ctx, user)\n\nAt no point is the existing account's password invalidated or the owner notified that a new OAuth identity was linked.\n\n## Attack Chain\n\n1. Attacker signs up with `victim@company.com` using email/password. Attacker sets a known password but does NOT click the email verification link. The account exists in the database with `EmailVerifiedAt = nil`.\n\n2. Some time later, the real owner of `victim@company.com` logs in via Google OAuth (a completely normal action).\n\n3. The OAuth callback at line 125 finds the attacker's existing account by email.\n\n4. At line 164, the Google OAuth identity is linked to the attacker's account.\n\n5. At line 179-181, the email is automatically verified (the attacker never verified it, but now it's marked as verified).\n\n6. At line 175, \"google\" is appended to the signup methods. The account now has both \"basic_auth\" and \"google\" as valid login methods.\n\n7. The attacker's original password is still valid in the database. It was never cleared, changed, or invalidated.\n\n8. The attacker logs in with `victim@company.com` and the password they originally set. They now have full access to the victim's account, including any data the victim added via their Google session.\n\n## Why This Is Zero-Click\n\nThe victim performs no unusual action. They simply log in via their Google account, which is the expected, secure behavior. The attacker staged the account beforehand and gains access without any further interaction.\n\nThis is a classic Account Linking vulnerability (cited in OWASP authentication guidelines). The core logic flaw is a trust boundary violation. Authorizer correctly trusts that Google has verified the email address, but it incorrectly extends that trust to validate the password that was set by the unverified attacker. The attacker maintains persistent, password-based backdoor access to the victim's account, even if the victim later revokes Authorizer's OAuth access from their Google account settings. The password was set before Google was ever involved and is never invalidated by the linking process.\n\n## Impact\n\n- Full account takeover for any user who logs in via OAuth\n- Attacker maintains persistent password-based access even after the victim changes OAuth providers\n- All data the victim creates after OAuth login is accessible to the attacker\n- The victim has no indication their account was pre-staged\n- Affects every OAuth provider configured in Authorizer (Google, GitHub, Facebook, Apple, LinkedIn, Twitter, Discord, Twitch, Roblox, Microsoft)\n\n## Suggested Fix\n\nBefore linking an OAuth identity to an existing account, verify that the existing account's email is already verified:\n\n existingUser, err := h.StorageProvider.GetUserByEmail(ctx, refs.StringValue(user.Email))\n if err == nil {\n // Account exists. Only link if email is already verified.\n if existingUser.EmailVerifiedAt == nil {\n // Email not verified by original owner. Do NOT link.\n // Either: reject the login, or create a new separate account,\n // or delete the unverified account and create a fresh one for the OAuth user.\n }\n }\n\nAdditionally, when linking a new OAuth identity, invalidate any existing password on the account or require the user to re-authenticate via the original method.\n\n## Credit\nKoda Reef",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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-20260807033110-66fe488fd2a4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/authorizerdev/authorizer/security/advisories/GHSA-29rf-f4vv-pvq6"
}, {
"type" : "WEB",
"url" : "https://github.com/authorizerdev/authorizer/commit/66fe488fd2a4e7acf1e517334344d5e8f3ddd296"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/authorizerdev/authorizer"
}, {
"type" : "WEB",
"url" : "https://github.com/authorizerdev/authorizer/releases/tag/2.4.0-rc.16"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-287" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-14T15:36:15Z",
"nvd_published_at" : null
}
}