● Hex package
ash_authentication
Ash_authentication has 24 security advisories. The newest release any of them names as the fix is 5.0.0-rc.16, a pre-release.
As of , ash_authentication has 24 security advisories. The newest release any of them names as the fix is 5.0.0-rc.16, a pre-release.
Your version, and the version to upgrade to
| If you run | Upgrade to | Advisories |
|---|---|---|
| From 5.0.0-rc.0 before 5.0.0-rc.16 | 5.0.0-rc.16 | 22 advisories |
| Before 4.15.1 | 4.15.1 | 21 advisories |
Security advisories, newest first
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| CVE-2026-110826EEF-CVE-2026-110826 | AshAuthentication log_out_everywhere leaves sessions valid after a password reset or non-atomic password change | From 5.0.0-rc.0 before 5.0.0-rc.16; From 4.5.0 before 4.15.1 | 4.15.1, 5.0.0-rc.16 | |
| CVE-2026-118505EEF-CVE-2026-118505 | AshAuthentication brute_force_strategy does not limit sign-in and request actions defined on the resource | From 5.0.0-rc.4 before 5.0.0-rc.16 | 5.0.0-rc.16 | |
| CVE-2026-119215EEF-CVE-2026-119215 | AshAuthentication TOTP setup lets a user install their own authenticator secret on another user's account | From 5.0.0-rc.0 before 5.0.0-rc.16 | 5.0.0-rc.16 | |
| CVE-2026-86688EEF-CVE-2026-86688 | Session id is not renewed on authentication in ash_authentication, allowing session fixation | From 5.0.0-rc.0 before 5.0.0-rc.14; From 0.2.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-76949EEF-CVE-2026-76949 | Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.10.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-91039EEF-CVE-2026-91039 | dynamic_oidc identities are not namespaced by connection in ash_authentication, allowing cross-connection account takeover | From 5.0.0-rc.10 before 5.0.0-rc.14 | 5.0.0-rc.14 | |
| CVE-2026-88952EEF-CVE-2026-88952 | OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication | From 5.0.0-rc.10 before 5.0.0-rc.14; From 4.14.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-85500EEF-CVE-2026-85500 | `require_confirmed_with` is not enforced on the action and fails open on an unreadable attribute in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.3.8 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-86533EEF-CVE-2026-86533 | Revoked session accepted because the session jti is never checked in AshAuthentication and AshAuthentication Phoenix | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.9.1 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-81632EEF-CVE-2026-81632 | Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix | From 5.0.0-rc.0 before 5.0.0-rc.14; From 3.10.5 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-80218EEF-CVE-2026-80218 | Sign-in token minted for one resource accepted by another in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 3.10.5 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-78223EEF-CVE-2026-78223 | Token revocation record built from unverified JWT claims in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 0.2.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-86522EEF-CVE-2026-86522 | Log injection via an unescaped password reset identity in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.2.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-81637EEF-CVE-2026-81637 | Replayable OAuth2 CSRF state retained after a failed callback in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 0.6.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-82761EEF-CVE-2026-82761 | Magic link single-use tokens replayable via TOCTOU race in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 3.9.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-82685EEF-CVE-2026-82685 | Confirmation token accepted on any record in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.14; From 0.5.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-82760EEF-CVE-2026-82760 | Superlinear base62 decoding exhausts CPU and memory in AshAuthentication API key sign-in | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.8.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-82759EEF-CVE-2026-82759 | Reversible IP address pseudonymisation in AshAuthentication audit log hash mode | From 5.0.0-rc.0 before 5.0.0-rc.14; From 4.12.0 before 4.15.0 | 4.15.0, 5.0.0-rc.14 | |
| CVE-2026-82723EEF-CVE-2026-82723 | Actor record with password digest stored in AshAuthentication audit log entries | From 5.0.0-rc.0 before 5.0.0-rc.2; From 4.12.0 before 4.15.0 | 4.15.0, 5.0.0-rc.2 | |
| CVE-2026-65633EEF-CVE-2026-65633 | Purpose-limited JWT accepted as full bearer authentication in AshAuthentication | From 5.0.0-rc.0 before 5.0.0-rc.13; From 3.10.5 before 4.14.2 | 4.14.2, 5.0.0-rc.13 | |
| CVE-2026-66882EEF-CVE-2026-66882 | Reflected XSS in AshAuthentication confirmation and magic link interaction forms | From 5.0.0-rc.0 before 5.0.0-rc.13; From 4.8.0 before 4.14.2 | 4.14.2, 5.0.0-rc.13 | |
| CVE-2026-49757GHSA-777c-2fxx-qr28, EEF-CVE-2026-49757 | AshAuthentication vulnerable to OAuth2/OIDC account takeover via email-based user matchingCritical severity | From 5.0.0-rc.0 before 5.0.0-rc.10; From 0.1.0 before 4.14.0 | 4.14.0, 5.0.0-rc.10 | |
| CVE-2025-32782GHSA-3988-q8q7-p787 | ash_authentication has email link auto-click account confirmation vulnerabilityModerate severity | Before 4.7.0 | 4.7.0 | |
| CVE-2025-25202GHSA-qrm9-f75w-hg4c | Ash Authentication has flawed token revocation checking logic in actions generated by `mix ash_authentication.install`Moderate severity | From 4.1.0 before 4.4.9 | 4.4.9 |