dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-56082

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

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
Capgo (Cap-go/capgo) before 12.128.2 contains an improper access control vulnerability in the SECURITY DEFINER PostgREST RPC function public.record_build_time, which is granted to the anon role and callable with only the public Supabase publishable (sb_publishable_*) anon key. An unauthenticated attacker can insert rows into public.build_logs for arbitrary organizations and, because the function uses ON CONFLICT (build_id, org_id) DO UPDATE, can overwrite existing usage/billing records by reusing the same build_id for a target org. This enables cross-tenant tampering of billing build logs and financial-impact denial of service by inflating billable build time.

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

A SECURITY DEFINER PostgREST RPC function (public.record_build_time) in Capgo before 12.128.2 is incorrectly granted EXECUTE permission to the public anon role, allowing any caller with just the Supabase publishable key to insert or update billing/build log records for any organization via the ON CONFLICT DO UPDATE clause, enabling cross-tenant data tampering and billing inflation.

MitigationUpgrade to Capgo version 12.128.2 or later, which should contain the fix. Alternatively, immediately revoke the function from the anon role and restrict execution to authenticated roles only.

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
None

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

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. Check Capgo version
    Locate your Capgo installation and identify its version number, then compare it to the affected range: versions before 12.128.2
    Affected if The installed Capgo version is lower than 12.128.2
  2. Verify the vulnerable function exists
    Query the PostgreSQL database for the function: SELECT proname FROM pg_proc WHERE proname = 'record_build_time' AND pronamespace = (SELECT oid FROM pg_namespace WHERE nspname = 'public');
    Affected if The function public.record_build_time exists in your database
  3. Check if anon role has EXECUTE permission
    Query function permissions: SELECT grantee, privilege_type FROM information_schema.function_privileges WHERE function_schema = 'public' AND function_name = 'record_build_time' AND grantee = 'anon';
    Affected if The anon role has EXECUTE permission on public.record_build_time
  4. Confirm function uses SECURITY DEFINER
    Query function attributes: SELECT prosrc FROM pg_proc WHERE proname = 'record_build_time' AND pronamespace = (SELECT oid FROM pg_namespace WHERE nspname = 'public'); then check for SECURITY DEFINER in the output or run: SELECT proname, prosecuritydefiner FROM pg_proc WHERE proname = 'record_build_time';
    Affected if The function is defined as SECURITY DEFINER (prosecuritydefiner = true)
  5. Test cross-tenant access capability
    Using the Supabase anon (publishable) key, attempt to call the function with an organization_id different from what your current session would normally allow, or inspect the function body to see if it accepts an organization_id parameter that can be set to any value
    Affected if The function accepts an organization_id parameter and the anon role can execute it without proper organization ownership validation

Your environment is affected if you run a Capgo version before 12.128.2 AND the public.record_build_time function exists with EXECUTE granted to the anon role as a SECURITY DEFINER function, allowing unauthenticated cross-tenant data manipulation.

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, which should contain the fix. Alternatively, immediately revoke the function from the anon role and restrict execution to authenticated roles only.

Recommended fix High confidence

12.128.2

  1. 1. Identify the current version of Capgo (Cap-go/capgo) in use by checking the deployed version
  2. 2. Upgrade Capgo to version 12.128.2 or later, as the vulnerability affects versions before 12.128.2
  3. 3. After upgrading, verify that the public.record_build_time function no longer permits unauthorized access from the anon role
  4. 4. Review and audit the public.build_logs table for any suspicious or unauthorized entries that may have been inserted during any potential exploitation

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56082 — 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-56082 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