Quick answers
- Is CVE-2026-110826 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110826 being exploited in the wild.
- How severe is CVE-2026-110826?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Team-Alembic Ash Authentication 4.5.0 to 4.15.0, 5.0.0-rc.0 to 5.0.0-rc.15.
- Is there a fix for CVE-2026-110826?
- Yes: fixed in ash_authentication 4.15.1, 5.0.0-rc.16. Until then: Ensure password change actions are implemented as atomic transactions, or manually implement global session invalidation in password change handlers. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110826 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110826?
- Check whether you run Team-Alembic Ash Authentication at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ash_authentication 4.15.1, 5.0.0-rc.16
Ensure password change actions are implemented as atomic transactions, or manually implement global session invalidation in password change handlers.
Technical details
The vulnerability is an improper session invalidation flaw in the LogOutEverywhere transformer. The condition guarding session revocation (where: changing(hashed_password)) is evaluated before the before_action hook that sets the new password hash, causing it to evaluate as false during non-atomic password changes. Both the default password reset action and installer-provided change_password action are non-atomic, leaving stored tokens unrevoked.
Affected products
- team-alembic ash_authentication 4.5.0 to 4.15.0, 5.0.0-rc.0 to 5.0.0-rc.15
Timeline
- 2026-11-03: disclosed