CVE-2026-86533
Critical 9.1No known exploitationFix availableRevoked session accepted because the session jti is never checked in AshAuthentication and AshAuthentication Phoenix
Record last updated
CVSS score
Critical on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 61% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Insufficient Session Expiration vulnerability in team-alembic AshAuthentication and AshAuthentication Phoenix allows a revoked session to remain fully authenticated. A resource configured with session_identifier :jti and require_token_presence_for_authentication? disabled stores its session value as : . The jti is there so that signing out can revoke that one session. Neither reader consults it: AshAuthentication.Plug.Helpers.authenticate_resource_from_session/4 and AshAuthentication.Phoenix.LiveSession.on_mount/4 both split the value with split_identifier/2, discard the jti and pass the bare subject to AshAuthentication.subject_to_user/3, which reloads the record. The token-presence branch of each function does check its token, calling AshAuthentication.TokenResource.Actions.get_token/3 with the jti and the purpose user. Because the revocation record is never read, neither its revoked state nor its expiry constrains the session, so a session captured before sign-out keeps working. This issue affects ash_authentication: from 4.9.1 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14; ash_authentication_phoenix: from 2.10.0 before 2.17.4 and from 3.0.0-rc.0 before 3.0.0-rc.11.
Weakness: CWE-613
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| team-alembic | ash_authentication | from 4.9.1 before 4.15.0 | 4.15.0 | CVE Program |
| team-alembic | ash_authentication | from 5.0.0-rc.0 before 5.0.0-rc.14 | 5.0.0-rc.14 | CVE Program |
| team-alembic | ash_authentication | fcaeb73f76f8f2e9aef8bf637690d2a20dd97596 | Not documented | CVE Program |
| team-alembic | ash_authentication_phoenix | from 0135217e34e621dac79ae3d9559aeee49304b0aa before 0135217e34e621dac79ae3d9559aeee49304b0aa | 0135217e34e621dac79ae3d9559aeee49304b0aa | CVE Program |
| team-alembic | ash_authentication_phoenix | from 2.10.0 before 2.17.4 | 2.17.4 | CVE Program |
| team-alembic | ash_authentication_phoenix | from 3.0.0-rc.0 before 3.0.0-rc.11 | 3.0.0-rc.11 | CVE Program |
| team-alembic | ash_authentication_phoenix | a3253fb4fc7145aeb403537af1c24d3a8d51ffb1 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit a3f49f7 in team-alembic/ash_authentication (opens in a new tab)patch
- Fix commit e28e911 in team-alembic/ash_authentication (opens in a new tab)patch
- https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-w374-hvrx-66hg (opens in a new tab)related, vendor-advisory
- Fix commit f7ab005 in team-alembic/ash_authentication_phoenix (opens in a new tab)patch
- https://github.com/team-alembic/ash_authentication_phoenix/security/advisories/GHSA-m6x4-4gvp-xwjr (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-86533 (opens in a new tab)related
- Introducing commit fcaeb73 in team-alembic/ash_authentication (opens in a new tab)related
- Introducing commit 0135217 in team-alembic/ash_authentication_phoenix (opens in a new tab)related
- Introducing commit a3253fb in team-alembic/ash_authentication_phoenix (opens in a new tab)related
- OSV record EEF-CVE-2026-86533 (opens in a new tab)related