cve.bz

CVE-2026-110826 team-alembic ash authentication

6.3 mediumEPSS 0.5%Fix available

Medium (6.3) in team-alembic ash authentication. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in ash_authentication 4.15.1, 5.0.0-rc.16.

On this page
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.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash_authentication (Hex): fixed in 4.15.1, 5.0.0-rc.16

Ask an AI about this CVE

Show the promptExplain CVE-2026-110826 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110826?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110826?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110826 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
team-alembic ash_authenticationfrom 4.5.0 before 4.15.1
team-alembic ash_authenticationfrom 5.0.0-rc.0 before 5.0.0-rc.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-110826Hexash_authentication>=4.5.0 <4.15.1
>=5.0.0-rc.0 <5.0.0-rc.16
4.15.1, 5.0.0-rc.16
EEF-CVE-2026-110826v5.0.0-rc.15, v5.0.0-rc.14, v4.15.0, v4.14.2, v5.0.0-rc.13 and 62 moreno fix published

References

Check your stackJSON