CVE-2026-91039— ash_authentication 动态 OIDC 跨连接账户接管漏洞
一分钟漏洞结论
影响对象
team-alembic ash_authentication
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
team-alembic 的 ash_authentication 中存在通过伪造进行身份认证绕过的漏洞。该漏洞允许控制动态 OIDC 策略中某个身份提供商连接的攻击者，冒充通过另一个连接建立的本地用户进行登录。 该策略的设计初衷是通过将每一行 记录中的 字段写入为 的形式，从而确保每个连接都拥有独立的身份命名空间。然而，这种命名空间机制实际上并未生效。 仅在 中为每个请求构建的临时运行时结构中被赋值，而 会通过 从编译时 DSL 重新获取策略，导致返回的是已持久化的结构体，其 值仍为 定义的默认值 。因此， 在写
可能的 ATT&CK 技术 1 AI
T1078 · Valid Accounts
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-91039 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
dynamic_oidc identities are not namespaced by connection in ash_authentication, allowing cross-connection account takeover
来源: CVE Program / CVE List V5
Vulnerability Description
Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who operates one identity-provider connection of a dynamic_oidc strategy to be signed in as a local user established through a different connection.
The strategy is meant to keep each connection in its own identity namespace by writing every UserIdentity row's strategy field as "<name>/<connection_id>", but that namespacing never takes effect. __connection_id__ is populated only on the ephemeral runtime struct built per request in dynamic_oidc/plug.ex, and DynamicOidc.IdentityChange.change/3 re-fetches the strategy from the compile-time DSL through Info.strategy_for_action, yielding the persisted struct whose __connection_id__ is its defstruct default of nil. OAuth2.identity_strategy_name/1 therefore falls back to the bare strategy name for both the identity write and the reads in oauth2/user_resolver.ex and oauth2/sign_in_preparation.ex. Since the identity resource's unique key is (uid, strategy), one row exists per sub across every connection, and the identity-match branch runs before any email check. Neither strategy handles iss, so nothing else distinguishes the issuers: OpenID Connect Core section 5.7 makes sub unique only within an issuer, so two connections numbering subjects independently share one subject space.
This issue affects ash_authentication: from 5.0.0-rc.10 before 5.0.0-rc.14.
来源: CVE Program / CVE List V5
CVSS Information
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
来源: CVE Program / CVE List V5
Vulnerability Type
使用欺骗进行的认证绕过
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| team-alembic | ash_authentication | 5.0.0-rc.10 ~ 5.0.0-rc.14 |
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
|
|
| team-alembic | ash_authentication | 64530644f9b37ebb76ca14aeb83a77597a0034b7 ~ 73ad16e452670bbf843550a13361bd41e72ad964 |
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
|
|
二、漏洞 CVE-2026-91039 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-91039 的情报信息
请登录查看更多情报信息。
CVE-2026-91039 厂商安全公告 (3)
同批安全公告 · team-alembic · 2026-09-17 · 共 14 条
| CVE-2026-82761 | 9.1 CRITICAL | AshAuthentication 令牌重放竞态漏洞 |
| CVE-2026-86533 | 9.1 CRITICAL | AshAuthentication Phoenix已吊销会话接收漏洞 |
| CVE-2026-85500 | 9.1 CRITICAL | Ash Authentication require_confirmed_with未强制校验漏洞 |
| CVE-2026-88952 | 9.1 CRITICAL | AshAuthentication OAuth2 账户链接逻辑缺陷 |
| CVE-2026-82760 | 8.2 HIGH | AshAuthentication API 密钥登录资源耗尽漏洞 |
| CVE-2026-82685 | 7.6 HIGH | AshAuthentication 确认令牌通用漏洞 |
| CVE-2026-80218 | 7.6 HIGH | AshAuthentication 登录令牌跨资源复用漏洞 |
| CVE-2026-81632 | 7.2 HIGH | AshAuthenticationPhoenix 一次性令牌重定向泄露漏洞 |
| CVE-2026-78223 | 6.9 MEDIUM | AshAuthentication 凭据撤销记录 JWT 验证漏洞 |
| CVE-2026-86522 | 6.3 MEDIUM | AshAuthentication 日志注入漏洞 |
| CVE-2026-81637 | 2.3 LOW | AshAuthentication 2.0.0 重放式CSRF漏洞 |
| CVE-2026-82723 | 1.8 LOW | AshAuthentication 审计日志记录密码摘要 |
| CVE-2026-82759 | 1.8 LOW | AshAuthentication审计日志哈希模式IP脱敏可逆漏洞 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-91039
暂无评论