CVE-2026-86533: CWE-613 Insufficient Session Expiration in team-alembic ash_authentication
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.
AI Analysis
Technical Summary
The vulnerability arises because a resource configured with session_identifier :jti and with require_token_presence_for_authentication? disabled stores session values as <jti>:<subject>. However, the session authentication functions discard the jti (token identifier) and only use the subject to reload the user record, ignoring token revocation and expiry states. Only when token presence enforcement is enabled does the code check the token's revocation status. As a result, sessions revoked by sign-out remain valid if token presence enforcement is disabled, allowing continued authenticated access with a revoked session token. This affects ash_authentication_phoenix versions from 2.10.0 before 2.17.4 and from 3.0.0-rc.0 onward, and ash_authentication versions from 4.9.1 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.
Potential Impact
An attacker or user with a revoked session token can continue to access resources as an authenticated user because the session revocation and expiry are not enforced when token presence enforcement is disabled. This undermines session invalidation mechanisms, potentially allowing unauthorized access after sign-out.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, enabling require_token_presence_for_authentication? is recommended to ensure token revocation is checked. Monitor vendor communications for updates and apply patches once released.
CVE-2026-86533: CWE-613 Insufficient Session Expiration in team-alembic ash_authentication
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.
CVSS v4.0
Score 9.1critical
Affected software
team-alembic
ash_authentication
team-alembic
ash_authentication
team-alembic
ash_authentication_phoenix
team-alembic
ash_authentication_phoenix
pkg:hex/ash_authenticationpkg:github/team-alembic/ash_authenticationpkg:hex/ash_authentication_phoenixpkg:github/team-alembic/ash_authentication_phoenixcpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*cpe:2.3:a:team-alembic:ash_authentication_phoenix:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because a resource configured with session_identifier :jti and with require_token_presence_for_authentication? disabled stores session values as <jti>:<subject>. However, the session authentication functions discard the jti (token identifier) and only use the subject to reload the user record, ignoring token revocation and expiry states. Only when token presence enforcement is enabled does the code check the token's revocation status. As a result, sessions revoked by sign-out remain valid if token presence enforcement is disabled, allowing continued authenticated access with a revoked session token. This affects ash_authentication_phoenix versions from 2.10.0 before 2.17.4 and from 3.0.0-rc.0 onward, and ash_authentication versions from 4.9.1 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.
Potential Impact
An attacker or user with a revoked session token can continue to access resources as an authenticated user because the session revocation and expiry are not enforced when token presence enforcement is disabled. This undermines session invalidation mechanisms, potentially allowing unauthorized access after sign-out.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, enabling require_token_presence_for_authentication? is recommended to ensure token revocation is checked. Monitor vendor communications for updates and apply patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-09-11T18:00:02.036Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aabe86a55bf5e2cf56c51cb
Added to database: 09/17/2026, 13:17:30 UTC
Last enriched: 09/17/2026, 13:31:29 UTC
Last updated: 09/18/2026, 00:46:20 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.