dbcve.org
CWE-320Weakness · CWE-320

CVE-2026-56254

HIGH · 7.0 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
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
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.

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

The capacitor-updater library before 12.128.2 improperly distributes private keys to all devices that download the app. Because the public key can be derived from the private key, an attacker with man-in-the-middle capability or who compromises the Capgo server can generate validly signed update bundles and trick devices into installing malicious updates not produced by the legitimate app developer.

MitigationUpgrade @capgo/capacitor-updater to version 12.128.2 or later, which should implement proper asymmetric key management where private keys are not distributed to client devices.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L

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 capacitor-updater package location
    Locate the @capgo/capacitor-updater package in your project dependencies. Check package.json for the dependency entry under 'dependencies' or 'devDependencies'.
    Affected if The package is listed in your dependencies
  2. Retrieve installed version number
    Run 'npm list @capgo/capacitor-updater' in your project root to display the installed version, or manually inspect node_modules/@capgo/capacitor-updater/package.json for the 'version' field.
    Affected if A version number is returned showing the package is installed
  3. Compare version against affected range
    Compare your installed version to the vulnerable range: versions before 12.128.2. Use semantic version comparison - any version where the major.minor.patch is lower than 12.128.2 (for example, 12.128.1, 12.127.0, any 11.x.x) is affected.
    Affected if Installed version is less than 12.128.2 (for example, 12.128.1, 12.100.0, 11.5.2)
  4. Verify updater is actively used
    Search your codebase for imports of @capgo/capacitor-updater (for example, 'import { ... } from @capgo/capacitor-updater' or ' CapacitorUpdater.') and check if the updater is initialized or configured in your app code.
    Affected if The updater is imported and used in your application code

You are affected if @capgo/capacitor-updater is installed with a version lower than 12.128.2 and your app uses the updater functionality.

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

Upgrade @capgo/capacitor-updater to version 12.128.2 or later, which should implement proper asymmetric key management where private keys are not distributed to client devices.

Recommended fix Moderate confidence

@capgo/capacitor-updater version 12.128.2 or later

  1. Check current installed version of @capgo/capacitor-updater in your project (e.g., npm list @capgo/capacitor-updater or package.json)
  2. Upgrade @capgo/capacitor-updater to version 12.128.2 or later using your package manager (e.g., npm install @capgo/capacitor-updater@^12.128.2 or yarn upgrade @capgo/capacitor-updater@^12.128.2)
  3. Verify the upgrade was successful by checking the installed version
  4. Test your app's update functionality to ensure the upgrade does not break existing behavior

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56254 — 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-56254 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