AshAuthentication log_out_everywhere leaves sessions valid after a password reset or non-atomic password change
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.15.1, 5.0.0-rc.16
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.15.1, 5.0.0-rc.16.
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
- Reach10/20Affects Hex packages
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
CVE-2026-110826 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects ash_authentication; fixed in 4.15.1 and 5.0.0-rc.16.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- Fix
- Fixed in 4.15.1, 5.0.0-rc.16
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
AshAuthentication, an Elixir authentication library for the Ash framework, is affected when its "log out everywhere" feature is enabled. A person who has stolen a victim's session token can remain signed in even after the victim resets or changes their password, because existing sessions are not invalidated in those cases.
Read the original description
Improper Session Invalidation after Authentication Credential Change vulnerability in team-alembic ash_authentication allows an attacker holding a victim's session token to stay signed in after the victim resets or changes their password. With apply_on_password_change? true, AshAuthentication.AddOn.LogOutEverywhere.Transformer adds OnPasswordChange to update actions as a global change guarded by where: changing(hashed_password). That condition is evaluated before the action's before_action hooks run, but AshAuthentication.Strategy.Password.HashPasswordChange sets the new hash in a before_action hook, so for every non-atomic password change the condition is false and the user's stored tokens are not revoked. The generated password reset action and the installer's change_password action are both non-atomic. This issue affects ash_authentication: from 4.5.0 before 4.15.1 and from 5.0.0-rc.0 before 5.0.0-rc.16.
What to do
Upgrade to a fixed version: 4.15.1, 5.0.0-rc.16.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ash_authenticationHex
From 4.5.0 · fixed in 4.15.1; From 5.0.0-rc.0 · fixed in 5.0.0-rc.16
- team-alembic/ash_authentication
Version range not reported
- ash_authenticationHex
From 4.5.0 · fixed in 4.15.1; From 5.0.0-rc.0 · fixed in 5.0.0-rc.16
Evidence 6
- Advisory
- Patch
- Patch
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110826
Is CVE-2026-110826 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-110826?
ash_authentication (Hex): from 4.5.0 before 4.15.1; from 5.0.0-rc.0 before 5.0.0-rc.16. ash_authentication (Hex): from 4.5.0 before 4.15.1; from 5.0.0-rc.0 before 5.0.0-rc.16.Source: cve.now feed data
How do I fix CVE-2026-110826?
Upgrade to a fixed version: 4.15.1, 5.0.0-rc.16.Source: cve.now feed data