Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-88861— Capgo AAL1 Session MFA Bypass via Direct RBAC Authorization

Quick assessment

Affected
Cap-go capgo.app
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Capgo（Cap-go/capgo.app）存在一个身份验证绕过漏洞，该漏洞影响所有版本（在发布时没有已修复的版本）。Edge 授权路径允许仅通过密码认证的 Supabase AAL1（Authentication Assurance Level 1）会话行使特权 RBAC 权限，即使该账户拥有已验证的多因素认证（MFA）因子但该因子未被当前会话使用。具体来说，Edge JWT 中间件（位于 中的 ）接受 JWT 令牌时，未验证其认证保障级别（assurance level）；而直接的 RBAC 路径（位于 中的

CVSS 8.3 · High

Possible ATT&CK Techniques 1 AI

T1556 · Modify Authentication Process
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-88861

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Capgo AAL1 Session MFA Bypass via Direct RBAC Authorization
Source: CVE Program / CVE List V5
Vulnerability Description
Capgo (Cap-go/capgo.app) contains an authentication bypass affecting all versions (no patched version available at time of publication). The Edge authorization path allows a password-only Supabase aal1 session to exercise privileged RBAC permissions even when the account has a verified MFA factor that has not been used for the session: the Edge JWT middleware (foundJWT() in supabase/functions/_backend/utils/hono_middleware.ts) accepts the JWT without validating its assurance level, and the direct RBAC path (checkPermission()/checkPermissionPg() in supabase/functions/_backend/utils/rbac.ts calling public.rbac_check_permission_direct()) authorizes by user ID without passing or checking the session aal, unlike the public.verify_mfa() control which correctly requires aal2. An attacker who knows only the victim's password can therefore authenticate, mint a persistent app-scoped app_admin API key that remains valid after the aal1 session is logged out, and perform privileged operations such as modifying production OTA channel configurations (validated by changing a public production channel from bundle 1.0.0 to 1.0.1), defeating the protection provided by MFA.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
使用候选路径或通道进行的认证绕过
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Cap-go capgo.app - -

II. Public POCs for CVE-2026-88861

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-88861

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-88861 (2)

Same Patch Batch · Cap-go · 2026-09-10 · 5 CVEs total

CVE-2026-88864 9.1 CRITICAL Capgo SSO Provider Authentication Bypass via PostgREST Direct Write
CVE-2026-88862 8.8 HIGH Capgo API Key Manager Authentication Bypass via x-limited-key-id
CVE-2026-88863 8.1 HIGH capgo.app through 12.207.1 Privilege Escalation via invite_new_user_to_org
CVE-2026-88860 6.3 MEDIUM Capgo Authorization Bypass via Stale Channel Permission Overrides

IV. Related Vulnerabilities

Same product: capgo.app
Same vendor: Cap-go
Same weakness: CWE-288

V. Comments for CVE-2026-88861

No comments yet

Leave a comment