Skip to content
Threat Brief

← All advisories

CVE-2026-86533

Critical 9.1No known exploitationFix available

Revoked session accepted because the session jti is never checked in AshAuthentication and AshAuthentication Phoenix

Record last updated

CVSS score

9.1

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.9%

Higher than 61% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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

VendorProductAffected versionsFixed inPer
team-alembicash_authenticationfrom 4.9.1 before 4.15.04.15.0CVE Program
team-alembicash_authenticationfrom 5.0.0-rc.0 before 5.0.0-rc.145.0.0-rc.14CVE Program
team-alembicash_authenticationfcaeb73f76f8f2e9aef8bf637690d2a20dd97596Not documentedCVE Program
team-alembicash_authentication_phoenixfrom 0135217e34e621dac79ae3d9559aeee49304b0aa before 0135217e34e621dac79ae3d9559aeee49304b0aa0135217e34e621dac79ae3d9559aeee49304b0aaCVE Program
team-alembicash_authentication_phoenixfrom 2.10.0 before 2.17.42.17.4CVE Program
team-alembicash_authentication_phoenixfrom 3.0.0-rc.0 before 3.0.0-rc.113.0.0-rc.11CVE Program
team-alembicash_authentication_phoenixa3253fb4fc7145aeb403537af1c24d3a8d51ffb1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references