# CVE-2026-56319: Capgo - App Existence Oracle via GET /statistics/app/:app_id

> Attackers can enumerate valid application IDs outside their authorized scope by analyzing differential error responses from the statistics endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-73p9-mprg-7r75, GHSA-r945-3x7m-hrjx

## What is CVE-2026-56319?

CVE-2026-56319 is a medium-severity vulnerability in Capgo, published on 20 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 an information disclosure vulnerability in the GET /statistics/app/:app_id endpoint that allows app-limited API keys to distinguish existing sibling app IDs through differential error responses. Attackers can enumerate real app IDs outside their allowed scope by observing 500 PGRST116 errors for inaccessible apps versus 401 errors for nonexistent apps, breaking tenant isolation.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2026-56319 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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