Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and…

CVSS 3.1 · [email protected] · Secondary 6.0 MEDIUMCVSS 3.1 · [email protected] · Primary 8.5 HIGHCheck source for fixed versionsKEV status unknown

Historical advisory recorded 24 Oct 2026 22:17:10 UTC. Read the latest advisory.

nvd · CVE-2023-29198

Published

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using `contextIsolation` and `contextBridge` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. This issue is only exploitable if an API exposed to the main world via `contextBridge` can return an object or array that contains a javascript object which cannot be serialized, for instance, a canvas rendering context. This would normally result in an exception being thrown `Error: object could not be cloned`. The app side workaround is to ensure that such a case is not possible. Ensure all values returned from a function exposed over the context bridge are supported. This issue has been fixed in versions `25.0.0-alpha.2`, `24.0.1`, `23.2.3`, and `22.3.6`.

Read the publisher's advisory

Affected versions, risk and source history

nvd · CVE-2023-29198

Published

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using `contextIsolation` and `contextBridge` are affected. This is a context isolation bypass, meaning that code …

Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps using `contextIsolation` and `contextBridge` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. This issue is only exploitable if an API exposed to the main world via `contextBridge` can return an object or array that contains a javascript object which cannot be serialized, for instance, a canvas rendering context. This would normally result in an exception being thrown `Error: object could not be cloned`. The app side workaround is to ensure that such a case is not possible. Ensure all values returned from a function exposed over the context bridge are supported. This issue has been fixed in versions `25.0.0-alpha.2`, `24.0.1`, `23.2.3`, and `22.3.6`.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-754

Original publisher date fields

published: 2023-09-06T21:15:11.560

lastModified: 2026-06-17T05:49:35.453

17 source CPE criteria · context only
  • cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha2:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha3:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha4:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha5:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha6:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:alpha7:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta6:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:24.0.0:beta7:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:25.0.0:alpha1:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
6 Sep 2023 21:15:11 UTC
Source modified
17 Jun 2026 05:49:35 UTC
Saved here
24 Oct 2026 22:17:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L

CVSS 3.1 · [email protected] · Primary · 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current