CVE-2026-91039
validatedZero produced an exploit or a check.GHSA-73j9-m294-fvv9 ↗EUVD-2026-81687 ↗
description
ash_authentication dynamic_oidc versions 5.0.0-rc.10 through 5.0.0-rc.13 can treat the same subject identifier from different identity-provider connections as one local identity. An attacker operating one configured identity provider may sign in as a user from another connection when their subject identifiers collide; deployments using dynamic_oidc with multiple connections are affected.
mitigation
Upgrade ash_authentication to 5.0.0-rc.14 and relink existing UserIdentity strategy values to their connection-specific namespaces before users sign in. For multi-connection deployments, compare subject identifiers across identity providers out of band and investigate accounts associated with collisions.
fixed in 5.0.0-rc.14
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-09-17 15:19Zghsa: trigger signal, started the run
- 2026-09-17 15:19Zcve.org record for CVE-2026-91039
this entry in the feed
GET /api/v1/feed/CVE-2026-91039
{ "etk_id": "ETK-2026-4479", "cve_id": "CVE-2026-91039", "display_id": "CVE-2026-91039", "ghsa_id": "GHSA-73j9-m294-fvv9", "euvd_id": "EUVD-2026-81687", "status": "published", "anchor_state": "anchored", "title": "Cross-connection identity collision in ash_authentication dynamic_oidc", "summary": "ash_authentication dynamic_oidc versions 5.0.0-rc.10 through 5.0.0-rc.13 can treat the same subject identifier from different identity-provider connections as one local identity. An attacker operating one configured identity provider may sign in as a user from another connection when their subject identifiers collide; deployments using dynamic_oidc with multiple connections are affected.", "mitigation": "Upgrade ash_authentication to 5.0.0-rc.14 and relink existing UserIdentity strategy values to their connection-specific namespaces before users sign in. For multi-connection deployments, compare subject identifiers across identity providers out of band and investigate accounts associated with collisions.", "vendor": "erlang", "product": "ash_authentication", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 5.0.0-rc.9, <= 5.0.0-rc.13" ], "ecosystem": "erlang", "fixed_versions": [ "5.0.0-rc.14" ], "package_name": "ash_authentication", "purl": "pkg:hex/ash_authentication" } ], "cwes": [ 287 ], "cvss_score": 9.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "epss_score": 0.0066, "epss_percentile": 0.5232, "epss_asof": "2026-11-17", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 23.22474903333333, "t0_at": "2026-09-17T15:19:15.994000+00:00", "signals": { "check": { "at": "2026-11-14T18:30:02.201578+00:00", "days": 58.132479254375, "is_lower_bound": false, "measured_at": "2026-09-17T15:19:15.994000+00:00", "url": null }, "trigger_signal": { "at": "2026-09-17T15:19:15.994000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-09-17T15:19:15.994000+00:00", "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-73j9-m294-fvv9" } } }
published 2026-11-14 18:14Z
last change 2026-11-18 21:29Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.