CVE-2026-56213
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 · uneditedCapgo before 12.128.2 contains an authorization bypass vulnerability in the public.upsert_version_meta SECURITY DEFINER function exposed via PostgREST RPC, allowing unauthenticated attackers to insert arbitrary rows into version_meta for any app_id. Attackers can exploit this by calling the RPC endpoint with a public anon key to poison storage metrics, causing persistent false data in dashboards and triggering incorrect alerts across victim applications.
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 confidenceCapgo before 12.128.2 has an authorization bypass in the public.upsert_version_meta SECURITY DEFINER function exposed via PostgREST RPC. Because SECURITY DEFINER functions run with definer privileges and the function lacks proper access controls, unauthenticated attackers using only the public anon key can insert arbitrary rows into version_meta for any app_id, enabling metric poisoning.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo versionLocate the installed Capgo version by checking the package.json, Docker image tag, or the running application version endpoint. Compare this version number to 12.128.2.Affected if The installed version is lower than 12.128.2.
-
Verify PostgREST RPC exposureConfirm that PostgREST is configured and the public.upsert_version_meta function is exposed as an RPC endpoint in the PostgREST configuration. Check the database schema for the function definition.Affected if The upsert_version_meta function exists and is callable via PostgREST RPC.
-
Inspect function security definitionQuery the database for the function definition: SELECT prosrc FROM pg_proc WHERE proname = 'upsert_version_meta'; Check if the function was created with SECURITY DEFINER privileges.Affected if The function uses SECURITY DEFINER and lacks additional access control checks within its body.
-
Check anon role permissionsQuery database permissions: SELECT proname, proacl FROM pg_proc WHERE proname = 'upsert_version_meta'; Verify if the public or anon role has execute permissions on this function.Affected if The anon role or public schema has execute permission on the upsert_version_meta function.
-
Audit version_meta table for unauthorized entriesQuery the version_meta table: SELECT app_id, created_at, key, value FROM version_meta ORDER BY created_at DESC LIMIT 100; Look for entries with unexpected app_id values or suspicious timestamp patterns indicating mass insertion.Affected if There are version_meta entries with app_id values that do not belong to legitimate applications or show signs of automated mass insertion.
A user is affected if their Capgo installation is version 12.128.2 or earlier, the upsert_version_meta function is exposed via PostgREST with SECURITY DEFINER and anon access, and unauthorized entries exist in the version_meta table.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Capgo 12.128.2 or later to patch the authorization bypass. Additionally, review and restrict the PostgREST RPC function permissions to ensure proper authentication and authorization are enforced.
Capgo 12.128.2 or later
- 1. Identify the current Capgo installation version
- 2. Upgrade Capgo to version 12.128.2 or later to address the authorization bypass vulnerability
- 3. Verify the upgrade was successful by checking the version
- 4. Confirm that the public.upsert_version_meta function no longer allows unauthenticated access via PostgREST RPC
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-56213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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