CVE-2026-80218

published 17 Sep 2026 · updated 19 Nov 2026

Sign-in token minted for one resource accepted by another in AshAuthentication

7.6HighCVSS 7.6EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in *, 4.15.0 and 5.0.0-rc.14.

Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker holding a sign-in token for one authenticated resource to be signed in as a user of a different resource. AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 parses the JWT sub claim (for example user?id=1) with URI.parse/1 and keeps only its query string, discarding the path segment that names the subject the token was issued for. Nothing else restores that binding: AshAuthentication.Jwt.verify/3 checks the signature, exp, nbf, jti and the library-version claims, the purpose check only requires sign_in, and the remaining comparison is over primary-key field names, which are identical across resources. The WebAuthn sign-in and remember-me preparations carry copies of the same helper and drop the path in the same way. The magic link sign-in path pins the subject name against the resource and is not affected. This issue affects ash_authentication: from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
team-alembic=eca8cadea0f1595ed2c10a0c177b1da9aa9e5269, >=3.10.5 <4.15.0, >=5.0.0-rc.0 <5.0.0-rc.14*, 4.15.0, 5.0.0-rc.14

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80218 severity on Zeptric[![CVE-2026-80218](https://zeptric.io/badge/cve/CVE-2026-80218.svg)](https://zeptric.io/cve/CVE-2026-80218)