CVE-2026-85500
Critical 9.1No known exploitationFix available`require_confirmed_with` is not enforced on the action and fails open on an unreadable attribute in AshAuthentication
Record last updated
CVSS score
Critical on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 56% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Authentication Bypass by Primary Weakness vulnerability in team-alembic AshAuthentication allows an unconfirmed user to obtain a session, defeating a mandatory email confirmation requirement. AshAuthentication.Strategy.Password.Actions.check_user/2 decides whether the attribute named by require_confirmed_with is set using a bare is_nil(Map.get(user, value)). When that attribute is not selected on the loaded record Map.get/2 returns %Ash.NotLoaded{}, and when a field policy denies it for the current actor it returns %Ash.ForbiddenField{}. Neither is nil, so the rejection branch is skipped and sign-i require_confirmed_with is enforced in two places, and neither holds in every configuration. sign_in_with_token and register are checked only inside AshAuthentication.Strategy.Password.Actions, not on the action itself, so any caller that invokes the action directly skips the check. An API layer such as AshGraphql or AshJsonApi invokes the action directly, so this applies to the default configuration. Where a check does run it compares the confirmation attribute against nil. That attribute holds %Ash.NotLoaded{} or %Ash.ForbiddenField{} when it sets select_by_default?: false, when an API layer narrows the read's select, or when a field policy hides it from the sign-in actor. Neither struct is nil, so those configurations read every user as confirmed. This issue affects ash_authentication: from 4.3.8 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.
Weakness: CWE-305
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| team-alembic | ash_authentication | from 4.3.8 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 | 7d37bc6e4df6697b5813d2f373f0fdb08f813f98 | 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 1076639 in team-alembic/ash_authentication (opens in a new tab)patch
- Fix commit 17f4c25 in team-alembic/ash_authentication (opens in a new tab)patch
- https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-fc47-6pgw-wh22 (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-85500 (opens in a new tab)related
- Introducing commit 7d37bc6 in team-alembic/ash_authentication (opens in a new tab)related
- OSV record EEF-CVE-2026-85500 (opens in a new tab)related