CVE-2026-56254
Private keys distributed to devices allow forging signed app updates.
Is CVE-2026-56254 being exploited?
Not confirmed. CVE-2026-56254 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.
How severe is CVE-2026-56254?
CVE-2026-56254 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56254?
Yes. A fix has been recorded for CVE-2026-56254. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56254 affect?
CVE-2026-56254 affects @capgo/capacitor-updater (<12.128.2), Cap-go/capgo, Mobile apps using this updater, Devices running affected apps. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56254?
Upgrade to v12.128.2+, rotate keys, verify update signing
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker (via MITM or compromised server) can forge update signatures to push malicious updates, enabling remote code execution and device compromise.
Immediate action required
- affected< 12.128.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.