Is CVE-2026-80218 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-80218 being exploited in the wild.

How severe is CVE-2026-80218?

Informational severity, with a CVSS score of 7.5, published 17 September 2026.

Which products and versions are affected?

team-alembic AshAuthentication 3.10.5 before 4.15.0, 5.0.0-rc.0 before 5.0.0-rc.14.

Is there a fix for CVE-2026-80218?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-80218 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-80218?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-80218: team-alembic AshAuthentication token confusion between resources

CVE-2026-80218 · Severity: info · CVSS 7.5 · Published 2026-09-17

AshAuthentication is an authentication library used in Elixir web applications to manage user sign-in across different resources. A vulnerability allows an attacker with a valid sign-in token for one resource to gain unauthorized access as a user on a completely different resource. This could enable account takeover and unauthorized access to sensitive data without requiring additional credentials.

Quick answers

Is CVE-2026-80218 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-80218 being exploited in the wild.
How severe is CVE-2026-80218?: Informational severity, with a CVSS score of 7.5, published 17 September 2026.
Which products and versions are affected?: team-alembic AshAuthentication 3.10.5 before 4.15.0, 5.0.0-rc.0 before 5.0.0-rc.14.
Is there a fix for CVE-2026-80218?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-80218 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-80218?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an improper authentication issue in the JWT token parsing logic of AshAuthentication.Strategy.Password.SignInWithTokenPreparation. The extract_primary_keys_from_subject/2 function uses URI.parse/1 to extract the JWT subject claim but discards the path segment that identifies which resource the token was issued for, retaining only the query string. Subsequent validation (AshAuthentication.Jwt.verify/3) checks signature, expiration, and library version, but does not verify the resource binding. Since primary-key field names are identical across resources, an attacker can reuse a token from one resource to authenticate as a user on another. The vulnerability affects multiple sign-in preparations (Password, WebAuthn, remember-me) but not magic link sign-in. Patched versions are available starting at 4.15.0 and 5.0.0-rc.14.

Affected products

team-alembic AshAuthentication 3.10.5 before 4.15.0, 5.0.0-rc.0 before 5.0.0-rc.14

Timeline

2026-09-17: disclosed: CVE-2026-80218 published on NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.