CVE-2026-56337
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCapgo before 12.128.2 contains an information disclosure vulnerability in the public.exist_app_v2 RPC function that allows unauthenticated attackers to enumerate app_ids by calling POST /rest/v1/rpc/exist_app_v2 with arbitrary appid parameters. Remote attackers can exploit this SECURITY DEFINER function to determine whether specific app_ids exist in the public.apps table, enabling cross-tenant app enumeration and privacy violations.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCapgo before 12.128.2 has an information disclosure vulnerability in the public.exist_app_v2 RPC function. Unauthenticated attackers can call POST /rest/v1/rpc/exist_app_v2 with arbitrary appid parameters to enumerate whether specific app_ids exist in the public.apps table. As a SECURITY DEFINER function, it allows cross-tenant app enumeration without authentication, enabling privacy violations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Capgo versionQuery the Capgo application or database for the current version number (commonly found in application metadata, configuration tables, or package version)Affected if Version is lower than 12.128.2 (e.g., 12.100.0, 12.50.0, or any version before 12.128.2)
-
Verify exist_app_v2 RPC function existsQuery the database schema for the public.exist_app_v2 function (e.g., SELECT proname FROM pg_proc WHERE proname = 'exist_app_v2' in PostgreSQL)Affected if The function exists in the database schema
-
Confirm function security definitionCheck if exist_app_v2 is defined as SECURITY DEFINER (e.g., SELECT prosrc FROM pg_proc WHERE proname = 'exist_app_v2' or inspect function definition)Affected if Function is defined as SECURITY DEFINER (executes with privileges of the defining user rather than the calling user)
-
Test unauthenticated access to the RPC endpointSend a POST request to /rest/v1/rpc/exist_app_v2 with an arbitrary appid parameter without providing authentication credentialsAffected if The request succeeds and returns a response indicating whether the app_id exists or not (e.g., true/false or an error revealing app existence)
-
Check for cross-tenant authorization on the functionInspect the function logic and database permissions to determine if it validates tenant context or ownership before returning app existence informationAffected if The function returns app existence results for any app_id without verifying the caller has access to that tenant's data
A user is affected if their Capgo installation version is below 12.128.2 AND the exist_app_v2 RPC function is exposed and accessible without authentication, allowing unauthorized enumeration of app IDs across tenants.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Capgo version 12.128.2 or later. If immediate upgrade is not possible, restrict access to the exist_app_v2 RPC function and implement proper authentication and authorization checks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56337 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data