ZeroDay Findings
Sign inSign up

Findings

CVE-2026-86533

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

Published Sep 17, 2026 · corrected/updated Oct 13, 2026 · evidence confidence high

## Summary Insufficient Session Expiration vulnerability in team-alembic AshAuthentication and AshAuthentication Phoenix allows a revoked session to remain fully authenticated. A resource configured with and disabled stores its session value as . The is there so that signing out can revoke that one session. Neither reader consults it: and both split the value with , discard the and pass the bare subject to , which reloads the record. The token-presence branch of each function does check its token, calling with the and the purpose . 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.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-86533 is a unknown public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: ash_authentication (4.9.1 → 4.15.0); ash_authentication (4.9.1 → 4.15.0; 5.0.0-rc.0 → 5.0.0-rc.14); ash_authentication_phoenix (2.10.0 → 2.17.4); ash_authentication_phoenix (2.10.0 → 2.17.4; 3.0.0-rc.0 → 3.0.0-rc.11). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: no CVSS/EPSS yet. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-613. Sources contributing to this record: cve_org, github, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 17, 2026 · GitHub Advisory Database

    Detected

    ## Summary Insufficient Session Expiration vulnerability in team-alembic AshAuthentication and AshAuthentication Phoenix allows a revoked session to remain fully authenticated. A resource configured with and disabled stores its session value as . The is there so that signing out can revoke that one session. Neither reader consults it: and both split the value with , discard the and pass the bare s

  2. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication fixed in 4.15.0; ash_authentication_phoenix fixed in 2.17.4

  3. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication fixed in 4.15.0

  4. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication_phoenix fixed in 2.17.4

  5. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication fixed in 4.15.0; ash_authentication fixed in 5.0.0-rc.14; ash_authentication_phoenix fixed in 2.17.4; ash_authentication_phoenix fixed in 3.0.0-rc.11

  6. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication fixed in 4.15.0; 5.0.0-rc.0

  7. Oct 13, 2026 · GitHub Advisory Database

    Fix available

    ash_authentication_phoenix fixed in 2.17.4; 3.0.0-rc.0

  8. Oct 13, 2026 · GitHub Advisory Database

    Updated

    ## Summary Insufficient Session Expiration vulnerability in team-alembic AshAuthentication and AshAuthentication Phoenix allows a revoked session to remain fully authenticated. A resource configured with and disabled stores its session value as . The is there so that signing out can revoke that one session. Neither reader consults it: and both split the value with , discard the and pass the bare s

Affected

  • Hex ash_authentication4.9.1 → 4.15.0
  • Hex ash_authentication4.9.1 → 4.15.0; 5.0.0-rc.0 → 5.0.0-rc.14
  • Hex ash_authentication_phoenix2.10.0 → 2.17.4
  • Hex ash_authentication_phoenix2.10.0 → 2.17.4; 3.0.0-rc.0 → 3.0.0-rc.11

Sources

References