In @capgo/capacitor-updater (Cap-go/capgo) before 12.128.2, the end-to-end encryption scheme distributes the private key to each device that downloads the app. Because the public key can be derived from the private key, an attacker performing a man-in-the-middle attack or compromising the Capgo server can create a validly signed update bundle and cause devices to install an update not produced by the original app maker.
CVE-2026-56254
HIGHPre-NVD 7.07.0—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 7.0; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.0Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(high)
- EPSS
- —
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026Patch available. Sources: github.
generic
capacitor-updater - End-to-End Encryption Bypass via Private Key Distribution | Advisories | VulnCheck
https://www.vulncheck.com/advisories/capacitor-updater-end-to-end-encryption-bypass-via-private-key-distributiongithub Patch Available
End-to-end encryption vulnerability · Advisory · Cap-go/capgo · GitHub
https://github.com/Cap-go/capgo/security/advisories/GHSA-j2f4-4pfc-p8rxVendor Advisories for CVE-2026-56254(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 6× in last 7d / 6× 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.
- 2026-07-11 15:13 UTCEG score recompute
- 2026-07-11 15:13 UTCGHSA enrichment
- 2026-07-11 02:58 UTCEG score recompute
- 2026-07-11 02:58 UTCGHSA enrichment
- 2026-07-10 14:43 UTCEG score recompute
- 2026-07-10 14:42 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-56254?
CVE-2026-56254 is a high vulnerability published on July 10, 2026. In @capgo/capacitor-updater (Cap-go/capgo) before 12.128.2, the end-to-end encryption scheme distributes the private key to each device that downloads the app. Because the public key can be derived from the private key, an attacker performing a man-in-the-middle attack or compromising the Capgo…
When was CVE-2026-56254 disclosed?
CVE-2026-56254 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-56254?
CVE-2026-56254 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-56254?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56254, 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-56254
Is Your Infrastructure Affected by CVE-2026-56254?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.