# CVE-2026-56327: Capgo - Unauthenticated Organization Existence Oracle via public.invite_user_to_org RPC

> Unauthenticated attackers can enumerate existing organization IDs by observing distinct error responses from the invite_user_to_org RPC function.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-35q8-ghfg-vp6m, GHSA-443m-f58x-jx9j

## What is CVE-2026-56327?

CVE-2026-56327 is a medium-severity vulnerability in Capgo, published on 30 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 information disclosure vulnerability in the public.invite_user_to_org RPC function that allows unauthenticated attackers to enumerate organization existence by observing distinct error responses. Attackers can call the SECURITY DEFINER function with a publishable API key to determine if an organization ID exists based on NO_ORG versus NO_RIGHTS responses, enabling tenant enumeration attacks.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2026-56327 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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