# CVE-2026-56079: Capgo - Cross-Tenant Authorization Bypass via PostgREST Webhook Access

> Attackers can bypass tenant isolation to steal webhook secrets and forge events, compromising data integrity and confidentiality in Capgo.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-7hf5-4jq6-894f, GHSA-hj3h-v877-g5rx

## What is CVE-2026-56079?

CVE-2026-56079 is a high-severity missing authorization vulnerability in Capgo, published on 19 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 contains a cross-tenant authorization bypass vulnerability in PostgREST endpoints that allows org-scoped read API keys to access other tenants' webhook secrets and delivery logs. Attackers can query the webhooks and webhook_deliveries endpoints to exfiltrate HMAC signing secrets and delivery payloads, enabling forged webhook events against victim organizations.

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

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


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

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

## Is CVE-2026-56079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56079 is a high-severity missing authorization vulnerability in Capgo, published on 19 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-56079 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-56079/ (Markdown: https://insights.sbomify.com/CVE-2026-56079/index.md)
```

## Sources

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

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