# CVE-2026-56244: Capgo - Webhook Signing Secret Disclosure via Non-Admin API Key

> Non-admin API keys can read webhook signing secrets, allowing attackers to forge authenticated webhook events and bypass integrity checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-qrrx-x3qf-x87v

## What is CVE-2026-56244?

CVE-2026-56244 is a high-severity vulnerability in Capgo, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-56244?


## How do I fix CVE-2026-56244?

No fix has been published for CVE-2026-56244 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56244 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56244 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56244 and fix it if it is affected.

What it is: CVE-2026-56244 is a high-severity vulnerability in Capgo, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56244 exists.

Affected product: Capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56244/ (Markdown: https://insights.sbomify.com/CVE-2026-56244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56244
- OSV: https://osv.dev/vulnerability/CVE-2026-56244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56244/
Summaries are generated and may contain mistakes; the official description above is the record.