CVE-2026-100611— Capgo apikey_manager 角色权限提升漏洞
一分钟漏洞结论
影响对象
Cap-go capgo.app
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Capgo（capgo.app 后端，版本 ≤ 12.261.0）在限制 apikey_manager 组织角色可绑定到新建 API 密钥的角色方面存在缺陷。当仅持有 apikey_manager 角色（具备 org.manage_apikeys 和 org.read 权限）的已认证用户通过 POST /apikey 接口并使用 JWT 会话调用时，系统仅执行以下检查：org.manage_apikeys 权限验证、一个固定的可分配角色名称 deny-list（即 public/apikey/scope.ts 中的
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-100611 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Capgo apikey_manager Role Privilege Escalation via Incomplete Role Deny-list
来源: CVE Program / CVE List V5
Vulnerability Description
Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names (APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES in public/apikey/scope.ts), and a priority-rank comparison in createRoleBindingForPrincipal (private/role_bindings.ts). No check verifies that the caller actually holds the permissions conferred by the role being assigned. Because the deny-list omits the deploy roles app_developer, app_uploader, channel_developer and channel_uploader, and apikey_manager is seeded with priority_rank 78 — higher than those roles' ranks (68, 66, 58, 57) — the rank check also passes. As a result, an apikey_manager who cannot upload bundles or promote channels can mint an API key bound to a deploy role and use it to push arbitrary OTA JavaScript updates to all end users of the organization's apps. As of the advisory publication no patched version was available.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
特权管理不恰当
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-100611 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-100611 的情报信息
请登录查看更多情报信息。
CVE-2026-100611 厂商安全公告 (1)
CVE-2026-100611 其他参考 (1)
同批安全公告 · Cap-go · 2026-09-26 · 共 19 条
| CVE-2026-100619 | 8.8 HIGH | Capgo OTA app_versions.manifest 绕过导致的应用程序清单投毒漏洞 |
| CVE-2026-100614 | 8.8 HIGH | Capgo <12.244.1 跨租户图像覆盖漏洞 |
| CVE-2026-100623 | 8.8 HIGH | Capgo 认证绕过通过直接写入 PostgREST org_users 表 |
| CVE-2026-100617 | 8.8 HIGH | Cap-Go Authorization Bypass via channel_permission_overrides |
| CVE-2026-100615 | 8.8 HIGH | Capgo 12.267.1 前 API 密钥轮换提权漏洞 |
| CVE-2026-100618 | 8.5 HIGH | Capgo App Icon 更新特权提升漏洞 |
| CVE-2026-100627 | 8.1 HIGH | Capgo bundle promotion API 通道RBAC权限绕过漏洞 |
| CVE-2026-100622 | 7.5 HIGH | Capgo.app < 12.129.0 已删除捆绑包缓存恢复漏洞 |
| CVE-2026-100612 | 7.2 HIGH | Capgo SSO Provider ID认证绕过漏洞 |
| CVE-2026-100625 | 7.1 HIGH | Capgo Build Upload Proxy 授权绕过漏洞 |
| CVE-2026-100629 | 5.5 MEDIUM | Capgo后台<12.127.5权限提升漏洞 |
| CVE-2026-100616 | 5.5 MEDIUM | capgo.app PostgREST customer_id 认证绕过漏洞 |
| CVE-2026-100624 | 5.4 MEDIUM | Capgo.app 12.264.5之前构建上传过期绕过漏洞 |
| CVE-2026-100613 | 5.3 MEDIUM | capgo.app 通道权限覆盖导致授权绕过漏洞 |
| CVE-2026-100626 | 4.3 MEDIUM | Capgo通过PUT /app图标端点越权访问12.128.2 |
| CVE-2026-100628 | 4.3 MEDIUM | capgo.app 12.128.12 前 通过 apikey 绕过认证漏洞 |
| CVE-2026-100621 | 4.3 MEDIUM | Capgo Content-Lock 绕过漏洞 |
| CVE-2026-100620 | 3.8 LOW | Capgo CLI 7.98.2 过度权限漏洞 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-100611
暂无评论