CVE-2026-76949
Critical 9.1No known exploitationFix availableRemember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement
Record last updated
CVSS score
Critical on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 57% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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 " _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.
Weakness: CWE-290
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- Set require_token_presence_for_authentication? true on the authenticated resource's token configuration. store_in_session/2 then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource. Otherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| team-alembic | ash_authentication | from 4.10.0 before 4.15.0 | 4.15.0 | CVE Program |
| team-alembic | ash_authentication | from 5.0.0-rc.0 before 5.0.0-rc.14 | 5.0.0-rc.14 | CVE Program |
| team-alembic | ash_authentication | 3d3de314692558d06ec13945f857f00514e95a8c | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 9a34136 in team-alembic/ash_authentication (opens in a new tab)patch
- Fix commit b9568a5 in team-alembic/ash_authentication (opens in a new tab)patch
- GitHub Advisory (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-76949 (opens in a new tab)related
- Introducing commit 3d3de31 in team-alembic/ash_authentication (opens in a new tab)related
- OSV record EEF-CVE-2026-76949 (opens in a new tab)related