CVE-2026-80218: team-alembic ash_authentication · Improper Authentication
Affects team-alembic ash_authenticationSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 5.0.0-rc.14 or 4.15.0 soon.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% 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:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| team-alembicash_authentication | Affected
| Fixed in
|
| team-alembicash_authentication | Affected
| Fixed in
|
| team-alembicash_authentication | Affected
| Fixed in– |
Hexash_authenticationpkg:hex/ash_authenticationOther threats | Affected
| Fixed in
|
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
If you cannot patch yet, avoid using affected versions or apply any vendor-provided workarounds if available.
Description
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.
References
- github.com/team-alembic/ash_authentication/security/advisories/GHSA-3pr8-f99q-86hp (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-80218.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-80218 (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/eca8cadea0f1595ed2c10a0c177b1da9aa9e5269 (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/2640e1872e1fef4e4606e601bf00102cff784c03 (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/7baac243ca651eee127a84d672eee3fcff42e598 (opens in a new tab)