CVE-2026-76949

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

State
Published
Severity
9.1 Critical
Published
Sep 17, 2026
Updated
Sep 18, 2026
Reserved
Sep 17, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.09.1 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NEEF

Weaknesses

  • CWE-290 Authentication Bypass by Spoofing

Affected Products

ProductVersions
ash_authenticationteam-alembic
  • 4.10.0 to before 4.15.0Affected
  • 5.0.0-rc.0 to before 5.0.0-rc.14Affected
ash_authenticationteam-alembic
  • 3d3de314692558d06ec13945f857f00514e95a8c and laterAffectedfrom b9568a53b438247238b1c5a4f49c8d84650f4bbaNot affectedfrom 9a34136b844abe179da1075067cf2835c64dcc12Not affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.