CVE-2026-86533 Details
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 <jti>:<subject>. 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.
A vulnerability exists in team-alembic AshAuthentication and AshAuthentication Phoenix, allowing revoked sessions to remain authenticated. This issue arises when a resource is set to use 'session_identifier :jti' and 'require_token_presence_for_authentication?' is disabled, which is the default setting. In this configuration, the session value is stored as '<jti>:<subject>', but the 'jti' is never checked during the authentication process. As a result, sessions can continue to be used even after they have been revoked, creating a security risk.
Upgrade to AshAuthentication versions 4.15.0 or 5.0.0-rc.14, and AshAuthentication Phoenix versions 2.17.4 or 3.0.0-rc.11. If an immediate upgrade is not possible, 'require_token_presence_for_authentication?' can be set to true as a temporary measure.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 17, 2026CISA-ADP
Assessed Sep 17, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-613 | Insufficient Session Expiration | EEF |
Affected Products
| Product | Versions |
|---|---|
| team-alembic AshAuthentication | >= 4.9.1, < 4.15.0 (semver) >= 5.0.0-rc.0, < 5.0.0-rc.14 (semver) |
CPE
Remediation
| |
| team-alembic AshAuthentication Phoenix | >= 2.10.0, < 2.17.4 (semver) >= 3.0.0-rc.0, < 3.0.0-rc.11 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 17, 2026 | CVE Modified | CISA-ADP |
| Sep 17, 2026 | New CVE Received | EEF |
Volerion