Skip to main content
VulnerabilityPublished

CVE-2026-88952: team-alembic ash_authentication · Improper Authentication

Affects team-alembic ash_authenticationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 5.0.0-rc.14 or 4.15.0 as a priority.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.0-rc.14, 4.15.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade team-alembic ash_authentication to 5.0.0-rc.14 or 4.15.0.

Affected software

ProductAffectedFixed in
team-alembicash_authenticationAffected
  • >=5.0.0-rc.10 <5.0.0-rc.14
Fixed in
  • 5.0.0-rc.14
team-alembicash_authenticationAffected
  • >=4.14.0 <4.15.0
Fixed in
  • 4.15.0
team-alembicash_authenticationAffected
  • ≥ 64530644f9b37ebb76ca14aeb83a77597a0034b7, < 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459
  • ≥ 42edcd8ebb13fafbb168f12591d7518ce0611fec, < 738bf9f32f2aa0d1bb92ce9ca5c2476cb5710459
Fixed in–
Hexash_authenticationpkg:hex/ash_authenticationOther threatsAffected
  • >=4.14.0 <4.15.0
  • >=5.0.0-rc.10 <5.0.0-rc.14
Fixed in
  • 4.15.0
  • 5.0.0-rc.14

CPE configurations (1)

  • cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until then, consider disabling OAuth2 identity linking or restricting authentication flows that rely on unverified identity attributes.

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.

References

Community reviews

Loading reviews…