Is CVE-2026-86533 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-86533 being exploited in the wild.

How severe is CVE-2026-86533?

Informational severity, published 17 September 2026.

Which products and versions are affected?

Team-Alembic AshAuthentication Phoenix 2.10.0 to 2.17.3; 3.0.0-rc.0 to 3.0.0-rc.10.

Is there a fix for CVE-2026-86533?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-86533 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-86533?

Check whether you run Team-Alembic AshAuthentication Phoenix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-86533: team-alembic AshAuthentication session fixation in revoked sessions

CVE-2026-86533 · Severity: info · Published 2026-09-17

AshAuthentication, a user authentication library for the Elixir web framework, fails to properly revoke sessions after a user signs out. An attacker who captures a valid session cookie before the user logs out can continue using that session indefinitely, even after the legitimate user revokes it. This allows unauthorized access to user accounts and protected resources.

Vendors: Team-Alembic.

Quick answers

Is CVE-2026-86533 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-86533 being exploited in the wild.
How severe is CVE-2026-86533?: Informational severity, published 17 September 2026.
Which products and versions are affected?: Team-Alembic AshAuthentication Phoenix 2.10.0 to 2.17.3; 3.0.0-rc.0 to 3.0.0-rc.10.
Is there a fix for CVE-2026-86533?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-86533 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-86533?: Check whether you run Team-Alembic AshAuthentication Phoenix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a session fixation / insufficient session expiration bug in two components: AshAuthentication.Plug.Helpers.authenticate_resource_from_session/4 and AshAuthentication.Phoenix.LiveSession.on_mount/4. When a resource is configured with session_identifier :jti, the session stores a value as <jti>:<subject>. On session validation, both functions split this value, discard the jti (which identifies the specific revocation record), and reload the user from the database using only the subject. The jti is never consulted, so revoked sessions remain valid. The token-presence authentication path does check revocation status via AshAuthentication.TokenResource.Actions.get_token/3, but the session-only path does not. Affected versions: ash_authentication 4.9.1–4.14.x and 5.0.0-rc.0–5.0.0-rc.13; ash_authentication_phoenix 2.10.0–2.17.3 and 3.0.0-rc.0–3.0.0-rc.10. Patches are available in ash_authentication 4.15.0+, 5.0.0-rc.14+ and ash_authentication_phoenix 2.17.4+, 3.0.0-rc.11+.

Affected products

team-alembic AshAuthentication 4.9.1 to 4.14.x; 5.0.0-rc.0 to 5.0.0-rc.13
team-alembic AshAuthentication Phoenix 2.10.0 to 2.17.3; 3.0.0-rc.0 to 3.0.0-rc.10

Timeline

2026-09-17: published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.