# CVE-2026-56213: Capgo - Unauthenticated Cross-Tenant Metrics Poisoning via upsert_version_meta RPC

> Unauthenticated attackers can poison cross-tenant metrics via an exposed RPC endpoint, causing false data and incorrect alerts in Capgo update servers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-5495-g4j9-gjwq, GHSA-g4hx-x8gc-x6rw

## What is CVE-2026-56213?

CVE-2026-56213 is a medium-severity missing authorization vulnerability in Capgo, published on 20 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Capgo 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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-56213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56213 is a medium-severity missing authorization vulnerability in Capgo, published on 20 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56213 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-56213/ (Markdown: https://insights.sbomify.com/CVE-2026-56213/index.md)
```

## Sources

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

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