CVE-2026-56248
Unauthenticated DoS via capgo-backend audit_logs (PostgREST)
Is CVE-2026-56248 being exploited?
Not confirmed. CVE-2026-56248 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.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-56248?
CVE-2026-56248 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-56248?
Yes. A fix has been recorded for CVE-2026-56248. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56248 affect?
CVE-2026-56248 affects Cap-go capgo-backend (<12.128.12), Supabase PostgREST API, public.audit_logs endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56248?
Upgrade to 12.128.12 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated requests to public.audit_logs can exhaust DB resources, causing cascading HTTP 500 DoS across endpoints.
Patch when possible
- affected< 12.128.12
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.