PoC Monitor
← All CVEs
CVE-2026-88861published 10 Sep 2026 13:05 UTCData: JSON · API

Cap-go capgo.app

Capgo AAL1 Session MFA Bypass via Direct RBAC Authorization

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-288
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Cap-go capgo.app
  • <= *

Mitigation

The record names no fix. Check the vendor advisory below.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published10 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

1 pending

Pending 1
RepositoryCreatedStarsAssessment
franklincg/secdim-assurance-drift-challenge 11 Sep 2026 +21 h 0 Pending
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.