dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56244

HIGH · 7.1 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 →
77/100
Remediation priority · High
Remotely reachable 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
Capgo before 12.128.2 allows non-admin API keys to read webhook signing secrets via Supabase REST due to insufficient row-level security policies on the webhooks table. Attackers can retrieve the webhook secret and forge valid X-Capgo-Signature headers to send authenticated webhook events to configured receivers, breaking webhook authenticity and integrity.

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

Capgo before 12.128.2 has insufficient row-level security policies on the webhooks table in Supabase, allowing non-admin API keys to read webhook signing secrets via the REST API. Attackers can use these stolen secrets to forge valid X-Capgo-Signature headers, impersonating legitimate webhook events.

MitigationUpdate to Capgo 12.128.2 or later and rotate any exposed webhook signing secrets. Review and harden RLS policies on the webhooks table to ensure only admin-level users can access sensitive secret fields.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Check your Capgo version
    Query your Capgo installation or check the package.json/version file to determine the installed version of Capgo.
    Affected if The installed version is earlier than 12.128.2 (e.g., 12.128.1, 12.127.x, or any version below 12.128.2).
  2. Verify RLS policies on the webhooks table
    Access your Supabase dashboard, navigate to the Table Editor, select the webhooks table, and inspect the Row Level Security policies. Look for policies that control SELECT access to this table.
    Affected if Any RLS policy allows SELECT operations on the webhooks table for non-admin users or API keys, or if no policy exists to restrict access to admin-level principals only.
  3. Confirm sensitive fields exist in the webhooks table
    Examine the schema of the webhooks table in Supabase to identify columns that store webhook signing secrets or authentication tokens.
    Affected if The webhooks table contains columns that store signing secrets, API keys, or authentication tokens that should be restricted.
  4. Test API access with non-admin credentials
    Using a non-admin or low-privilege Capgo API key, make a GET request to the REST API endpoint for the webhooks table (e.g., POST /rest/v1/webhooks).
    Affected if The request returns rows containing signing secrets or other sensitive fields without requiring admin-level authentication.

You are affected if your Capgo version is below 12.128.2 AND the webhooks table in Supabase allows non-admin API keys to read signing secrets via the REST API.

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

Update to Capgo 12.128.2 or later and rotate any exposed webhook signing secrets. Review and harden RLS policies on the webhooks table to ensure only admin-level users can access sensitive secret fields.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify all Capgo deployments currently running versions before 12.128.2
  2. 2. Review the Capgo release notes or changelog for version 12.128.2 to confirm the security fix addresses the RLS policy vulnerability
  3. 3. Create a backup of the current database and configuration
  4. 4. Upgrade Capgo to version 12.128.2 or later using the standard upgrade procedure for your deployment method
  5. 5. After upgrade, verify that non-admin API keys can no longer access the webhooks table via the Supabase REST API
  6. 6. Rotate any webhook signing secrets that may have been exposed prior to the upgrade
  7. 7. Review API key permissions to ensure they follow the principle of least privilege
Caveat Review Capgo release notes for version 12.128.2 for any breaking changes between your current version and 12.128.2

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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