CVE-2026-76949— ash_authentication 会话替换漏洞
一分钟漏洞结论
影响对象
team-alembic ash_authentication
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Ash Authentication 中存在的“通过欺骗绕过身份验证”漏洞，允许能够向受害者浏览器植入 remember-me 令牌的攻击者，将受害者的已认证会话替换为攻击者自己账户的会话。 具体机制如下： 函数本应通过检查会话中是否存在 键来跳过对已登录访客的重新认证。然而， 函数仅在启用了 配置时才会写入该键；否则，它只会写入裸的主体名称（bare subject name）。在默认配置下，该守卫函数（guard）读取的键从未被写入，导致其“已登录”分支永远无法被执行。因此，remember-me 登录逻辑会在
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-76949 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement
来源: CVE Program / CVE List V5
Vulnerability Description
Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.
AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 skips re-authenticating an already-signed-in visitor by checking the session for "<subject_name>_token", but store_in_session/2 writes that key only when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in authenticate_resource_from_session/4 selects the key correctly, so the guard and the reader disagree about which key holds the session.
This issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 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 | 4.10.0 ~ 4.15.0 |
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
|
|
| team-alembic | ash_authentication | 3d3de314692558d06ec13945f857f00514e95a8c ~ * |
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
|
|
二、漏洞 CVE-2026-76949 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-76949 的情报信息
请登录查看更多情报信息。
CVE-2026-76949 补丁与修复 (2)
CVE-2026-76949 其他参考 (3)
-
EEF-CVE-2026-76949 - OSV related
-
CVE-2026-76949 related
同批安全公告 · team-alembic · 2026-09-17 · 共 16 条
| 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-91039 | 9.1 CRITICAL | ash_authentication 动态 OIDC 跨连接账户接管漏洞 |
| CVE-2026-82760 | 8.2 HIGH | AshAuthentication API 密钥登录资源耗尽漏洞 |
| CVE-2026-82685 | 7.6 HIGH | AshAuthentication 确认令牌通用漏洞 |
| CVE-2026-80218 | 7.6 HIGH | AshAuthentication 登录令牌跨资源复用漏洞 |
| CVE-2026-86688 | 7.4 HIGH | ash_authentication 会话固定漏洞 |
| 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-76949
暂无评论