CVE-2026-56307Medium· 4.3▾ TwilightPoC availableCap-go before 12.128.12 contains a broken cursor pagination vulnerability in the /private/devices endpoint on the Cloudflare/workerd path that allows authenticated attackers to cause duplicate-page loops and make later rows unreachable. …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 23.7 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.3%
Cap-go before 12.128.12 contains a broken cursor pagination vulnerability in the /private/devices endpoint on the Cloudflare/workerd path that allows authenticated attackers to cause duplicate-page loops and make later rows unreachable. Attackers with app.read_devices access can exploit non-advancing cursor filters to trigger infinite pagination loops, prevent dataset traversal, and cause repeated processing in device-management workflows.
capgo < 12.128.12Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-56073Critical· 9.4Cap-go - OTP Bypass via Response Manipulation in Email Verification
CVE-2026-56080Medium· 4.9Cap-go - Authentication Logic Flaw in Enforce Password Policy
CVE-2026-56081Critical· 9.1Cap-go - Account Lockout via 2FA Misconfiguration on Unverified Email
CVE-2026-56079Medium· 6.5Capgo - Cross-Tenant Authorization Bypass via PostgREST Webhook Access
CVE-2026-56082High· 7.5Capgo - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC
CVE-2026-56215High· 8.3Capgo - Account Merge via Poisoned public.users.email in SSO Provisioning