Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8amended

Electron: Sandboxed preload code cache can be poisoned by a compromised renderer

CVE-2026-102677GHSA-qmv3-fv6v-rmhq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 44.0.0-beta.6, 43.5.0, 42.10.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    >= 42.3.3, < 42.10.0>= 43.0.0-beta.1, < 43.5.0>= 44.0.0-alpha.1, < 44.0.0-beta.6
    Fixed in
    43.5.0, 44.0.0-beta.6, 42.10.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-102677: 0.10% estimated exploitation activity in the next 30 days; percentile 0.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact The cache Electron keeps for sandboxed preload scripts did not verify that a cached entry matched the preload it was served for. A compromised renderer could use this to run its own code in the preload context on a later load. Apps are only affected if they load untrusted content. Apps that do not load untrusted content are not affected. Workarounds There are no app side workarounds, you must update to a patched version of Electron. Fixed Versions 44.0.0-beta.6 43.5.0 42.10.0 For more information If you have any questions or comments about this advisory, email us at security@electronjs.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-qmv3-fv6v-rmhq

  2. Revision 2 · amended ·

    Amended from osv record GHSA-qmv3-fv6v-rmhq

  3. Revision 1 · created ·

    Published from ghsa record GHSA-qmv3-fv6v-rmhq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102677

Advisory: Electron: Sandboxed preload code cache can be poisoned by a compromised renderer
IDs: CVE-2026-102677, GHSA-qmv3-fv6v-rmhq
Record: https://patchnext.com/advisories/cve-2026-102677 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 44.0.0-beta.6, 43.5.0, 42.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected >= 42.3.3, < 42.10.0; >= 43.0.0-beta.1, < 43.5.0; >= 44.0.0-alpha.1, < 44.0.0-beta.6; fixed in 43.5.0, 44.0.0-beta.6, 42.10.0

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qmv3-fv6v-rmhq (GitHub-reviewed advisory GHSA-qmv3-fv6v-rmhq lists affected ranges: npm electron >=42.3.3 =43.0.0-beta.1 =44.0.0-alpha.1 <44.0.0-beta.6)
- Verified: https://osv.dev/vulnerability/GHSA-qmv3-fv6v-rmhq (OSV record GHSA-qmv3-fv6v-rmhq lists affected ranges: npm electron >=42.3.3 =43.0.0-beta.1 =44.0.0-alpha.1 <44.0.0-beta.6 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…