# CVE-2026-56243: Capgo - Hashed API Key Enforcement Bypass via PostgREST/RLS Plane

> Attackers bypass hashed API key enforcement by sending plaintext keys to the PostgREST plane, accessing protected resources in Capgo.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-2c7m-fxr4-462c, GHSA-6g74-8cpq-g2c8

## What is CVE-2026-56243?

CVE-2026-56243 is a high-severity authentication bypass vulnerability in Capgo, published on 23 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 security control bypass vulnerability where the PostgREST/RLS plane accepts plaintext API keys through the capgkey header despite enforce_hashed_api_keys being enabled. Attackers can bypass org-level hashed-key enforcement by sending plaintext API keys directly to the PostgREST/RLS plane to access protected resources.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-56243 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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