Skip to content
Fencer Intel
high 7.4

CVE-2026-102675 json

Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled

published last mo. modified 13d ago also EUVD-2026-89093 , GHSA-j84w-jfhq-vhvj

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

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI enabled but corsEnabled disabled could remain script-readable across origins. This residual issue completes the remediation for CVE-2026-70604. Applications are affected only when they expose such a scheme and load untrusted content in the same session. Schemes intentionally registered with corsEnabled enabled remain cross-origin readable by design. This issue is fixed in versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5.

Patch / fix

  • npm electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  • atom electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5
  • electronjs electron 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5

Is CVE-2026-102675 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-102675 updated cvss 7.4

electron: Electron: Cross-origin information disclosure via improper CORS enforcement in custom protocol handlers

  • Red Hat Build of Podman Desktop rh-podman-desktop Red Hat Enterprise Linux 10 podman-desktop, rh-podman-desktop
    affected: workaround, no fix available

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
partial
Assessed
last mo.

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm electron
<41.10.6
>=42.0.0-alpha.1, <42.9.2
>=43.0.0-alpha.1, <43.4.1
>=44.0.0-alpha.1, <44.0.0-beta.5
41.10.6
42.9.2
43.4.1
44.0.0-beta.5

Affected products

  • electron electron

Classification

Weakness

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.