CVE Watchtower

CVE-2026-91039team-alembic ash_authentication Authentication Bypass by Spoofing

NVD

Vulnerability Summary

Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who operates one identity-provider connection of a dynamic_oidc strategy to be signed in as a local user established through a different connection.

The strategy is meant to keep each connection in its own identity namespace by writing every UserIdentity row's strategy field as "<name>/<connection_id>", but that namespacing never takes effect. __connection_id__ is populated only on the ephemeral runtime struct built per request in dynamic_oidc/plug.ex, and DynamicOidc.IdentityChange.change/3 re-fetches the strategy from the compile-time DSL through Info.strategy_for_action, yielding the persisted struct whose __connection_id__ is its defstruct default of nil. OAuth2.identity_strategy_name/1 therefore falls back to the bare strategy name for both the identity write and the reads in oauth2/user_resolver.ex and oauth2/sign_in_preparation.ex. Since the identity resource's unique key is (uid, strategy), one row exists per sub across every connection, and the identity-match branch runs before any email check. Neither strategy handles iss, so nothing else distinguishes the issuers: OpenID Connect Core section 5.7 makes sub unique only within an issuer, so two connections numbering subjects independently share one subject space.

This issue affects ash_authentication: 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 19, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.66%Probability
Root Weakness (CWE)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
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 >= 5.0.0-rc.10 and < 5.0.0-rc.14
  • team-alembic ash_authentication >= 64530644f9b37ebb76ca14aeb83a77597a0034b7 and < 73ad16e452670bbf843550a13361bd41e72ad964
Patched Versions
  • team-alembic ash_authentication 5.0.0-rc.14
  • team-alembic ash_authentication 73ad16e452670bbf843550a13361bd41e72ad964

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 19, 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-91039. 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 19, 2026 13:08 UTC