Skip to content
Fencer Intel
high 7.8

CVE-2026-102677 json

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

published last mo. modified last mo. also EUVD-2026-89179 , GHSA-qmv3-fv6v-rmhq

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 42.3.3 until 42.10.0, 43.5.0, and 44.0.0-beta.6, Electron's sandboxed preload code cache did not verify that a cached entry matched the preload it was served for. A compromised renderer could write attacker-controlled cache data and cause Electron to reuse it for a later load, executing the renderer's code in the more privileged preload context. The issue affects applications that load untrusted content. This issue is fixed in versions 42.10.0, 43.5.0, and 44.0.0-beta.6.

Patch / fix

  • npm electron 42.10.0, 43.5.0, 44.0.0-beta.6
  • atom electron 42.10.0, 43.5.0, 44.0.0-beta.6
  • mozilla firefox 42.10.0, 43.5.0, 44.0.0-beta.6
  • electronjs electron 42.10.0, 43.5.0, 44.0.0-beta.6

Is CVE-2026-102677 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-102677 updated cvss 7.8

electron: Electron: Privilege escalation via sandboxed preload code cache poisoning

  • Red Hat Build of Podman Desktop rh-podman-desktop
    affected: workaround, no fix available “Disable loading untrusted web content within Electron renderer processes or isolate untrusted origins into dedicated web views with disabled preload scripts.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm electron
>=42.3.3, <42.10.0
>=43.0.0-beta.1, <43.5.0
>=44.0.0-alpha.1, <44.0.0-beta.6
42.10.0
43.5.0
44.0.0-beta.6

Affected products

  • electron electron

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.