CVE-2026-56296

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
15.1%
KEV
Not listed

Published

July 11, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 11, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Cap-go - App Existence Oracle via Unauthenticated transfer_app RPC | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cap-go-app-existence-oracle-via-unauthenticated-transfer-app-rpc
github Patch Available🟡 PoC Available

Unauthenticated app existence oracle via public.transfer_app RPC (distinct errors for existing vs non-existing app_id) · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-fmm3-3qcg-85j6

Vendor Advisories for CVE-2026-56296(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 11:58 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 12:17 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 12:36 UTCGHSA enrichment
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 12:56 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 13:15 UTCGHSA enrichment
  24. 2026-07-11 13:33 UTCEG score recompute
  25. 2026-07-11 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56296?
CVE-2026-56296 is a medium vulnerability published on July 11, 2026. Cap-go before 12.128.2 contains an information disclosure vulnerability in the public.transferapp 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…
When was CVE-2026-56296 disclosed?
CVE-2026-56296 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56296 actively exploited?
CVE-2026-56296 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56296?
CVE-2026-56296 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-56296?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56296, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56296

Explore →

Is Your Infrastructure Affected by CVE-2026-56296?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs