CVE Watchtower

CVE-2026-76949team-alembic ash_authentication Authentication Bypass by Spoofing

NVD

Vulnerability Summary

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.
Severity Level
CRITICAL(9.1)
Published Date
Sep 17, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.77%Probability
Root Weakness (CWE)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
CVSS v4.0 Base Metrics — Score 9.1 (CRITICAL)
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
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • team-alembic ash_authentication >= 4.10.0 and < 4.15.0
  • team-alembic ash_authentication >= 5.0.0-rc.0 and < 5.0.0-rc.14
  • team-alembic ash_authentication >= 3d3de314692558d06ec13945f857f00514e95a8c and < *
Patched Versions
  • team-alembic ash_authentication 4.15.0
  • team-alembic ash_authentication 5.0.0-rc.14
  • team-alembic ash_authentication *

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run team-alembic ash_authentication and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Sep 17, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new team-alembic ash_authentication CVEsYou are reading CVE-2026-76949. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More team-alembic ash_authentication CVEs

Data last checked: Nov 19, 2026 13:08 UTC