CVE-2026-88952
OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication
Published Sep 17, 2026 · updated Oct 13, 2026
## Summary Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker to be signed in as another user by linking an OAuth2 identity to an account that is not theirs. matches an existing account using the register action's keys, then gates linking the incoming provider identity to it on , which reads only the provider's boolean and never compares the provider's email value with the matched account's email. That gate assumes the account was matched by its email field, so under any other it is vacuous and an attacker presenting their own verified email is attached to, and issued a session for, an account matched on some other attribute. The same unguarded gate applies in on the path, where the account is matched by the sign-in action's read filter instead. The upsert also rewrites the matched account's email to the attacker's address, so later account recovery reaches the attacker rather than the owner. This issue affects ash_authentication: from 4.14.0 before 4.15.0 and from 5.0.0-rc.10 before 5.0.0-rc.14. ## Impact An attacker who controls a provider account with a verified email of their own is signed in as a different local user, holding a session bearing that user's subject, with no interaction from the victim and no need to pre-register. Because the link also rewrites the matched account's email to the attacker's address, account recovery for the victim is redirected to the attacker and the compromise survives the provider identity being unlinked. ## Workarounds Set on the affected strategy, which refuses the sign-in rather than linking it and closes both the register and the sign-in path. Alternatively, key the register action's , or the sign-in action's read filter, on the email attribute, which restores the premise the gate assumes. ## Configurations The strategy must have enabled, and the account must be matched on something other than the email: a register action whose keys are not the email attribute, or, with , a sign-in act
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 17, 2026 · GitHub Advisory Database
Detected
## Summary Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker to be signed in as another user by linking an OAuth2 identity to an account that is not theirs. matches an existing account using the register action's keys, then gates linking the incoming provider identity to it on , which reads only the provider's boolean and never compares the provider's email
Oct 13, 2026 · GitHub Advisory Database
Fix available
ash_authentication fixed in 4.15.0
Oct 13, 2026 · GitHub Advisory Database
Fix available
ash_authentication fixed in 4.15.0
Oct 13, 2026 · GitHub Advisory Database
Updated
## Summary Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker to be signed in as another user by linking an OAuth2 identity to an account that is not theirs. matches an existing account using the register action's keys, then gates linking the incoming provider identity to it on , which reads only the provider's boolean and never compares the provider's email
Affected
- Hex ash_authentication4.14.0 → 4.15.0
Sources
- CVE.orgVulnerability recordCVE-2026-88952
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-wc6x-276q-jrf9
GitHub Advisory Database record mirrored by OSV.
github.com - OSV.devPackage advisoryEEF-CVE-2026-88952
OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication
osv.dev