Authorizer Go Package: Zero-click Account Takeover Vulnerability
- Severity
- HIGH
- Affected component
- authorizer (go)
- Affected versions
- < 0.0.0-20260807033110-66fe488fd2a4
- Patched version
- Not yet available
An early warning has been issued for a critical vulnerability in the authorizer Go package that reportedly allows zero-click account takeover via OAuth identity linking to unverified email accounts.
What happened
The authorizer Go package is under investigation for a vulnerability that could allow an attacker to gain persistent access to a victim's account after a normal OAuth login. This is achieved by linking OAuth identities to unverified email accounts. The vulnerability affects versions prior to 0.0.0-20260807033110-66fe488fd2a4. The issue was first flagged on 2026-08-14T15:36:15+00:00 and is tracked under GHSA-29RF-F4VV-PVQ6.
To assess your exposure, check if your application uses the authorizer Go package and verify the version in use. If you are using a version prior to 0.0.0-20260807033110-66fe488fd2a4, you may be at risk. It is recommended to review and update the package to ensure email addresses are verified before linking OAuth identities.
What to do about it
- Review your application's dependencies to identify if the authorizer Go package is in use.
- Check the version of the authorizer Go package currently in use in your application.
- If you are using a version prior to 0.0.0-20260807033110-66fe488fd2a4, update the package to a non-vulnerable version as soon as possible.
- Ensure that email addresses are verified before linking OAuth identities in your application.
- Monitor the primary sources for updates on the vulnerability and any official fixes that may be released.
How 0Day would have caught this
authorizer is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You may be affected if your application uses the authorizer Go package and the version is prior to 0.0.0-20260807033110-66fe488fd2a4.
What should I do right now?
Review your application's dependencies, check the version of the authorizer Go package, and update to a non-vulnerable version if necessary. Ensure email verification before OAuth identity linking.
Is there an official fix available?
No official fix has been published yet. Monitor the primary sources for updates.