Vulnerability advisory

CVE-2026-76949

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

Published Updated OSV record ↗

Also known as EEF-CVE-2026-76949GHSA-hh34-374j-pfr5

Severity
  • CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/team-alembic/ash_authentication ↗
3d3de314692558d06ec13945f857f00514e95a8c to before b9568a53b438247238b1c5a4f49c8d84650f4bbab9568a53b438247238b1c5a4f49c8d84650f4bba
5f8ce8ac5b0d0ce5a92bc8b474551fc7a8d228e7 to before d6b2be35cf8f0b8ab84e7a934cfb0d91de0a3c17d6b2be35cf8f0b8ab84e7a934cfb0d91de0a3c17
6767fe27eb952e5bc09aa2e5a7d8f96f5a1c424a to before fea75958a081ed337ceb578396174039694c48dffea75958a081ed337ceb578396174039694c48df
Not specified3d3de314692558d06ec13945f857f00514e95a8c
Not specified9a34136b844abe179da1075067cf2835c64dcc12
Also listed as affected (28)
  • v4.14.2
  • v5.0.0-rc.13
  • v4.14.1
  • v5.0.0-rc.12
  • v5.0.0-rc.11
  • v5.0.0-rc.10
  • v4.14.0
  • v4.13.7
  • 5.0.0-rc.9
  • 5.0.0-rc.8
  • v5.0.0-rc.7
  • v5.0.0-rc.6
  • v5.0.0-rc.5
  • v5.0.0-rc.4
  • v5.0.0-rc.3
  • v5.0.0-rc.2
  • v5.0.0-rc.1
  • v5.0.0-rc.0
  • v4.13.6
  • v4.13.5
  • v4.13.4
  • v4.13.3
  • v4.13.2
  • v4.13.1
  • v4.13.0
  • v4.12.0
  • v4.11.0
  • v4.10.0

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.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools