---
id: CVE-2026-88861
title: >-
  Capgo (Cap-go/capgo.app) contains an authentication bypass affecting all
  versions (no patched version available at time of publication)
summary: >-
  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…
severity: high
cvss: 8.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L'
cwe:
  - CWE-288
vendor: Cap-go
product: capgo.app
affected:
  - capgo.app
published: '2026-09-10'
updated: '2026-09-15'
sourceUpdated: '2026-09-15T15:17:25.277'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-88861'
references:
  - url: >-
      https://github.com/Cap-go/capgo.app/security/advisories/GHSA-9435-5xw9-v29h
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/capgo-aal1-session-mfa-bypass-via-direct-rbac-authorization
    label: disclosure@vulncheck.com
  - url: >-
      https://github.com/Cap-go/capgo.app/security/advisories/GHSA-9435-5xw9-v29h
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - exploit-available
  - cve.org
epss: 0.00523
epssPercentile: 0.419
exploits:
  github: 1
  githubRepos:
    - 'https://github.com/franklincg/secdim-assurance-drift-challenge'
  checkedAt: '2026-09-26T09:06:04.419Z'
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-15T14:13:22.833448Z'
ingestedAt: '2026-09-10T13:50:37.334Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.