CVE-2026-88952
Critical 9.1No known exploitationFix availableOAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication
Record last updated
CVSS score
Critical on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 56% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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. AshAuthentication.Strategy.OAuth2.UserResolver.resolve/3 matches an existing account using the register action's upsert_identity keys, then gates linking the incoming provider identity to it on email_trusted?/2, which reads only the provider's email_verified 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 upsert_identity 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 OAuth2.SignInPreparation on the registration_enabled? false 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.
Weakness: CWE-287
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Vendor solution
- Upgrading prevents new links but does not unpick existing ones. An account already linked through this path stays linked, and a victim's email may already have been rewritten to the attacker's address. Operators whose register action or sign-in action matched on anything other than the email should review their UserIdentity rows for links whose provider email does not match the linked account's email, and check affected accounts for a rewritten email address.
- Mitigation
- Set trust_email_verified? false 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 upsert_identity, or the sign-in action's read filter, on the email attribute, which restores the premise the gate assumes. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| team-alembic | ash_authentication | from 4.14.0 before 4.15.0 | 4.15.0 | CVE Program |
| team-alembic | ash_authentication | from 42edcd8ebb13fafbb168f12591d7518ce0611fec before 2bd630eef8b7c8ae1e90e8fd43ba12fbc7e256ba | 2bd630eef8b7c8ae1e90e8fd43ba12fbc7e256ba | CVE Program |
| team-alembic | ash_authentication | from 5.0.0-rc.10 before 5.0.0-rc.14 | 5.0.0-rc.14 | CVE Program |
| team-alembic | ash_authentication | from 64530644f9b37ebb76ca14aeb83a77597a0034b7 before 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459 | 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 2bd630e in team-alembic/ash_authentication (opens in a new tab)patch
- Fix commit 738bf9f in team-alembic/ash_authentication (opens in a new tab)patch
- GitHub Advisory (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-88952 (opens in a new tab)related
- Introducing commit 42edcd8 in team-alembic/ash_authentication (opens in a new tab)related
- Introducing commit 6453064 in team-alembic/ash_authentication (opens in a new tab)related
- OSV record EEF-CVE-2026-88952 (opens in a new tab)related