Skip to main content
VulnerabilityPublished

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

Affects team-alembic ash_authenticationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 5.0.0-rc.14 or 4.15.0 as a priority.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.0-rc.14, 4.15.0, 3.0.0-rc.11 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade ash_authentication to 5.0.0-rc.14 or 4.15.0; ash_authentication_phoenix to 3.0.0-rc.11 or 2.17.4.

Affected software

ProductAffectedFixed in
team-alembicash_authenticationAffected
  • >=5.0.0-rc.0 <5.0.0-rc.14
Fixed in
  • 5.0.0-rc.14
team-alembicash_authenticationAffected
  • >=4.9.1 <4.15.0
Fixed in
  • 4.15.0
team-alembicash_authenticationAffected
  • ≥ fcaeb73f76f8f2e9aef8bf637690d2a20dd97596, < a3f49f758f013d2ff086dd9c5ef2d94e921711b4
Fixed in–
team-alembicash_authentication_phoenixAffected
  • >=3.0.0-rc.0 <3.0.0-rc.11
Fixed in
  • 3.0.0-rc.11
team-alembicash_authentication_phoenixAffected
  • >=2.10.0 <2.17.4
Fixed in
  • 2.17.4
team-alembicash_authentication_phoenixAffected
  • ≥ a3253fb4fc7145aeb403537af1c24d3a8d51ffb1, < f7ab005a2aac09707a25521653c94893d328cc52
  • ≥ 0135217e34e621dac79ae3d9559aeee49304b0aa, < f7ab005a2aac09707a25521653c94893d328cc52
Fixed in–

CPE configurations (2)

  • cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
  • cpe:2.3:a:team-alembic:ash_authentication_phoenix:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, enabling require_token_presence_for_authentication? is recommended to ensure token revocation is checked.

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.

References

Community reviews

Loading reviews…