ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-86533

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

Published Sep 17, 2026 · catalog updated Oct 13, 2026 · Revoked session accepted because

Check if you run it

No confirmed exploitation is on record for CVE-2026-86533. EPSS is 0.91%. Act only if a listed version of Revoked session accepted because is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Revoked session accepted because).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.91%
Remediation
Advisory link
Affected products
Hex ash_authentication · Hex ash_authentication_phoenix

## 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • 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

How to fix CVE-2026-86533

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-86533. EPSS is 0.91%. Act only if a listed version of Revoked session accepted because is installed.

Which versions are affected?

Compare what you have installed with 4.9.1 → 4.15.0, 4.9.1 → 4.15.0; 5.0.0-rc.0 → 5.0.0-rc.14, 2.10.0 → 2.17.4, 2.10.0 → 2.17.4; 3.0.0-rc.0 → 3.0.0-rc.11. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-613: Insufficient Session Expiration. EPSS 0.91%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

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

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.