CVE Watchtower

CVE-2026-88952team-alembic ash_authentication Improper Authentication

NVD

Vulnerability 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.

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.
Severity Level
CRITICAL(9.1)
Published Date
Sep 17, 2026
Last Modified
Nov 20, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.75%Probability
Root Weakness (CWE)
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.
CVSS v4.0 Base Metrics — Score 9.1 (CRITICAL)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • team-alembic ash_authentication >= 4.14.0 and < 4.15.0
  • team-alembic ash_authentication >= 5.0.0-rc.10 and < 5.0.0-rc.14
  • team-alembic ash_authentication >= 42edcd8ebb13fafbb168f12591d7518ce0611fec and < 2bd630eef8b7c8ae1e90e8fd43ba12fbc7e256ba
  • team-alembic ash_authentication >= 64530644f9b37ebb76ca14aeb83a77597a0034b7 and < 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459
Patched Versions
  • team-alembic ash_authentication 4.15.0
  • team-alembic ash_authentication 5.0.0-rc.14
  • team-alembic ash_authentication 2bd630eef8b7c8ae1e90e8fd43ba12fbc7e256ba
  • team-alembic ash_authentication 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run team-alembic ash_authentication and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Sep 17, 2026Published
  • Nov 20, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new team-alembic ash_authentication CVEsYou are reading CVE-2026-88952. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More team-alembic ash_authentication CVEs

Data last checked: Nov 20, 2026 07:13 UTC