CVE Watchtower

CVE-2026-86533team-alembic ash_authentication Insufficient Session Expiration

NVD

Vulnerability Summary

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.
Severity Level
CRITICAL(9.1)
Published Date
Sep 17, 2026
Last Modified
Nov 20, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.91%Probability
Root Weakness (CWE)
According to WASC, Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.
CVSS v4.0 Base Metrics — Score 9.1 (CRITICAL)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • team-alembic ash_authentication >= 4.9.1 and < 4.15.0
  • team-alembic ash_authentication >= 5.0.0-rc.0 and < 5.0.0-rc.14
  • team-alembic ash_authentication >= fcaeb73f76f8f2e9aef8bf637690d2a20dd97596 and < *
  • team-alembic ash_authentication_phoenix >= 2.10.0 and < 2.17.4
  • team-alembic ash_authentication_phoenix >= 3.0.0-rc.0 and < 3.0.0-rc.11
  • team-alembic ash_authentication_phoenix >= 0135217e34e621dac79ae3d9559aeee49304b0aa and < 0135217e34e621dac79ae3d9559aeee49304b0aa
  • team-alembic ash_authentication_phoenix >= a3253fb4fc7145aeb403537af1c24d3a8d51ffb1 and < *
Patched Versions
  • team-alembic ash_authentication 4.15.0
  • team-alembic ash_authentication 5.0.0-rc.14
  • team-alembic ash_authentication *
  • team-alembic ash_authentication_phoenix 2.17.4
  • team-alembic ash_authentication_phoenix 3.0.0-rc.11
  • team-alembic ash_authentication_phoenix 0135217e34e621dac79ae3d9559aeee49304b0aa
  • team-alembic ash_authentication_phoenix *

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run team-alembic ash_authentication and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Sep 17, 2026Published
  • Nov 20, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new team-alembic ash_authentication CVEsYou are reading CVE-2026-86533. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More team-alembic ash_authentication CVEs

Data last checked: Nov 20, 2026 07:13 UTC