CVE-2026-80218
Last modified
CVE-2026-80218 is a high-severity vulnerability rated 7.6/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| team-alembic | ash_authentication | >= 3.10.5, < 4.15.0; >= 5.0.0-rc.0, < 5.0.0-rc.14 |
| team-alembic | ash_authentication | >= eca8cadea0f1595ed2c10a0c177b1da9aa9e5269, < * |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-80218?
How severe is CVE-2026-80218?
How do I fix CVE-2026-80218?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-80210FrontAccounting through 2.4.20 generates a CSRF token in end…6.5
- CVE-2026-80211FrontAccounting through 2.4.20 stores and verifies user pass…5.9
- CVE-2026-80212An issue was discovered in the resolv gem before 0.7.2 for R…7.5
- CVE-2026-80213An issue was discovered in the resolv gem before 0.7.2 for R…4
- CVE-2026-80214LibreNMS’s Virtualization Discovery module is vulnerable to …8.6
- CVE-2026-80217Hidden functionality issue exists in FF-RFI079I4 and FF-RFI0…8.7
- CVE-2026-80219A flaw was found in hawtio-operator. When deploying Hawtio i…8.7
- CVE-2026-8022Inappropriate implementation in MHTML in Google Chrome prior…3.1
- CVE-2026-80223Incorrect Authorization vulnerability in ash-project ash_gra…7.1
- CVE-2026-80225In NLnetLabs Unbound up to and including 1.26.0, a degradati…5.3
- CVE-2026-80227Incorrect Comparison vulnerability in ash-project ash_sql al…2.1
- CVE-2026-80229When performing transfers via libcurl’s multi interface, poo…7.5
Are you affected by CVE-2026-80218?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST