dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-56245

HIGH · 8.2 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER record_build_time RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/record_build_time with a public API key to poison billing and quota data for any organization, enabling resource exhaustion and cross-tenant billing manipulation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an authorization bypass vulnerability in Supabase Capgo's SECURITY DEFINER RPC function 'record_build_time' that allows unauthenticated attackers with only a public API key to insert arbitrary build-time records. The flaw enables poisoning of billing and quota data across organizations, leading to resource exhaustion and cross-tenant billing manipulation.

MitigationUpgrade to Capgo version 12.128.2 or later. Additionally, review and restrict the 'record_build_time' RPC function to enforce proper authentication and authorization checks, ensuring it cannot be called anonymously or with only a public API key.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Capgo version
    Check the installed Supabase Capgo version in your deployment. This is typically found in your package.json, dependency lock file, or the Capgo dashboard under account/settings. Compare the version number to the affected range: versions before 12.128.2 are vulnerable.
    Affected if The installed Capgo version is below 12.128.2
  2. Verify record_build_time RPC function exists
    Query your Supabase database for the record_build_time function definition. In PostgreSQL, run: SELECT proname, prosrc, prokind FROM pg_proc WHERE proname = 'record_build_time'; Also check its security definer status with: SELECT proname, prosecdef FROM pg_proc WHERE proname = 'record_build_time';
    Affected if The function exists and was created as SECURITY DEFINER (prosecdef = true) before the patch was applied
  3. Confirm function accessibility with public API key
    Test whether the record_build_time function can be invoked using only a public (anon) API key without authentication. Make an authenticated request to your Supabase edge function or RPC endpoint using only the public key and observe if the call succeeds.
    Affected if The function accepts calls with just a public API key and executes without requiring elevated privileges
  4. Review access logs for record_build_time calls
    Examine your Supabase database logs, edge function logs, or API gateway logs for invocations of the record_build_time function. Look for calls originating from unexpected sources, at unusual times, or with anomalous payload sizes that may indicate exploitation.
    Affected if Logs show record_build_time calls that were not initiated by your own legitimate build processes

You are affected if your Supabase Capgo version is below 12.128.2 AND the record_build_time function is accessible with only a public API key.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Capgo version 12.128.2 or later. Additionally, review and restrict the 'record_build_time' RPC function to enforce proper authentication and authorization checks, ensuring it cannot be called anonymously or with only a public API key.

Recommended fix High confidence

Supabase Capgo version 12.128.2 or later

  1. 1. Identify the current installed version of Supabase Capgo in your environment
  2. 2. Consult the official Supabase Capgo release notes or changelog to obtain version 12.128.2 or a later stable release
  3. 3. Follow the standard upgrade procedure for Supabase Capgo - typically via your package manager (npm/pnpm) or the Capgo dashboard
  4. 4. After upgrading, verify the record_build_time RPC function no longer accepts calls with only a public API key without proper organization-level authorization
  5. 5. Test that authenticated calls to /rest/v1/rpc/record_build_time properly enforce organization-scoped permissions
  6. 6. Monitor logs for any suspicious build-time record insertions that occurred before the patch
Caveat Review release notes for any breaking changes between your current version and 12.128.2; minor version jumps may include database migrations or API behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data