CVE-2026-56226
Unauthenticated API lets attackers retrieve other users' org membership and PII via public PostgREST RPC.
Is CVE-2026-56226 being exploited?
Not confirmed. CVE-2026-56226 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-56226?
CVE-2026-56226 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56226?
Yes. A fix has been recorded for CVE-2026-56226. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56226 affect?
CVE-2026-56226 affects Capgo (cap-go/capgo) < 12.128.2, Supabase PostgREST RPC public.get_orgs_v6, Apps using public publishable API key. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56226?
Upgrade to capgo 12.128.2, rotate publishable keys, audit logs and limit anon role permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker with public publishable API key can query RPC with arbitrary user UUID to exfiltrate org membership, roles, subscription/trial metadata and management_email (PII).
Immediate action required
- affected< 12.128.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.