CVE-2023-29198

Context isolation bypass via nested unserializable return value in Electron

HIGH
8.5
CVSS Score
Published: September 6, 2023 at 08:13 PM UTC
Updated: June 17, 2026 at 05:49 AM UTC
2 products affected across 2 vendorsElectronElectron

Using electron by electron?

Get instant alerts when new vulnerabilities affect electron - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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`.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 22.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2.3, so it looks safe — our inference, not a vendor statement
v < 22.3.6v < 23.2.3v < 24.0.1v < 25.0.0-alpha.2
Affected range stops below 22.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.0.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 25.0.0-alpha.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-754

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card