dbcve.org
CWE-203Weakness · CWE-203

CVE-2026-56296

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
Cap-go before 12.128.2 contains an information disclosure vulnerability in the public.transfer_app RPC function that returns distinct error messages for existing versus non-existing app IDs. Unauthenticated attackers can enumerate valid app IDs by observing error message differences when calling transfer_app with only the publishable API key.

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 confidence

Cap-go before version 12.128.2 has an information disclosure vulnerability in the public.transfer_app RPC function. The function returns distinct error messages depending on whether an app ID exists in the system. An unauthenticated attacker with only a publishable API key can exploit this to enumerate valid app IDs by observing different error responses.

MitigationStandardize error messages in the transfer_app function so that identical responses are returned regardless of whether the app ID exists, preventing enumeration. Consider rate limiting or additional authentication requirements for the RPC function.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cap-go installation version
    Locate the installed Cap-go version by checking the package.json, docker image tag, or the running service version endpoint if available. Compare this version number against the affected range (versions before 12.128.2).
    Affected if The installed version is lower than 12.128.2
  2. Verify public.transfer_app RPC function is exposed
    Check if the transfer_app RPC function is accessible externally. Review API gateway or route configurations to confirm the endpoint is exposed without authentication protection.
    Affected if The transfer_app function is accessible without authentication or with only a publishable API key
  3. Test error message differentiation
    Make two test requests to the transfer_app RPC endpoint using a valid app ID format and an invalid/non-existent app ID. Compare the error responses returned for each case.
    Affected if The error messages differ between existing and non-existing app IDs (e.g., one returns 'app not found' while the other returns a different message)
  4. Confirm publishable API key access
    Verify whether a publishable API key alone grants access to the transfer_app function without requiring full authentication.
    Affected if The function can be invoked using only a publishable API key without additional authentication

You are affected if your Cap-go version is below 12.128.2 AND the transfer_app RPC function is accessible with only a publishable API key AND it returns distinct error messages for existing vs non-existing app IDs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Standardize error messages in the transfer_app function so that identical responses are returned regardless of whether the app ID exists, preventing enumeration. Consider rate limiting or additional authentication requirements for the RPC function.

Recommended fix High confidence

Cap-go version 12.128.2 or later

  1. Upgrade Cap-go to version 12.128.2 or later to remediate the information disclosure vulnerability.
  2. After upgrading, verify that the public.transfer_app RPC function no longer returns distinct error messages for existing versus non-existing app IDs.
  3. Confirm that unauthenticated attackers can no longer enumerate valid app IDs through the transfer_app function using only a publishable API key.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56296 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56296 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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