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
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.
- High severity, but no confirmed exploitation yet
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)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
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 computedSeverity70% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.8%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026capacitor-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-distributionEnd-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 12× in last 7d / 32× 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-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 05:58 UTCGHSA enrichment
- 2026-07-16 17:44 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 05:29 UTCGHSA enrichment
- 2026-07-15 17:14 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 04:58 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 16:43 UTCGHSA enrichment
- 2026-07-14 04:28 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 16:13 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 03:58 UTCGHSA enrichment
Show 7 moreShow fewer
- 2026-07-12 15:43 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:28 UTCGHSA enrichment
- 2026-07-11 15:13 UTCGHSA enrichment
- 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(5)
What is CVE-2026-56254?
When was CVE-2026-56254 disclosed?
Is CVE-2026-56254 actively exploited?
What is the CVSS score of CVE-2026-56254?
How do I remediate CVE-2026-56254?
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.