CVE-2026-76949

published 17 Sep 2026 · updated 20 Nov 2026

Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement

9.1CriticalCVSS 9.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in *, 4.15.0 and 5.0.0-rc.14.

Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account. AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 skips re-authenticating an already-signed-in visitor by checking the session for "<subject_name>_token", but store_in_session/2 writes that key only when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in authenticate_resource_from_session/4 selects the key correctly, so the guard and the reader disagree about which key holds the session. This issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
team-alembic=3d3de314692558d06ec13945f857f00514e95a8c, >=4.10.0 <4.15.0, >=5.0.0-rc.0 <5.0.0-rc.14*, 4.15.0, 5.0.0-rc.14

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76949 severity on Zeptric[![CVE-2026-76949](https://zeptric.io/badge/cve/CVE-2026-76949.svg)](https://zeptric.io/cve/CVE-2026-76949)