Unrated

Zero-click account takeover in Authorizer OAuth identity linking

IdentifiersCVE-2026-35511CWE-306

CVE-2026-35511 is an account takeover vulnerability in Authorizer affecting OAuth identity linking logic. The flaw occurs when an OAuth identity is linked to an existing local account solely on the basis of a matching email address, without verifying that the pre-existing account's email address had already been validated by its legitimate owner. In the vulnerable workflow, an attacker can first create a local account using a victim's email address while leaving that account unverified. When the victim later authenticates through a legitimate OAuth provider using the same email address, the application links the OAuth identity to the attacker-created account. Because the attacker already controls the password-based credentials associated with that account, the attacker can retain access to the now-linked victim account. The issue is a logic flaw in account linking and identity proofing rather than memory corruption or injection.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in full account takeover. An attacker can obtain persistent password-based access to the victim's account after the victim completes a normal OAuth login flow. This can expose all data and functionality available to the compromised account, including profile information, application data, and any actions the victim is authorized to perform. Because the attacker can continue using the pre-established local credentials, access may persist even after the victim authenticates successfully through OAuth.

Mitigation

If you can’t patch tonight, do this now.

Until patched code is deployed, disable or restrict automatic account linking by email. Do not link an OAuth identity to an existing account unless the existing account's email has already been verified. If an unverified account exists for the same email address, reject the link, create a separate account, or remove the unverified account before proceeding. Require re-authentication or reset/invalidate existing local passwords when linking a new OAuth identity. Monitoring for suspicious account-linking events and forcing credential resets for potentially affected users can reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade github.com/authorizerdev/authorizer to version 0.0.0-20260807033110-66fe488fd2a4 or later. Correct the account-linking logic so that OAuth identities are linked only to accounts whose email addresses were previously verified by the rightful owner. Existing password-based credentials associated with accounts being linked should be invalidated, revalidated, or otherwise subjected to a secure re-authentication process to prevent attacker-retained access. Review existing linked accounts for cases where unverified local accounts may have been merged with OAuth identities and remediate affected accounts as needed.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity