Electron context isolation bypass via nested unserializable return value
Impact
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.
Workarounds
This issue is exploitable under either of two conditions:
- If an API exposed to the main world via
contextBridgecan return an object or array that contains a JS object which cannot be serialized, for instance, a canvas rendering context. This would normally result in an exception being thrownError: object could not be cloned. - If an API exposed to the main world via
contextBridgehas a return value that throws a user-generated exception while being sent over the bridge, for instance a dynamic getter property on an object that throws an error when being computed.
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 and that any objects returned from functions do not have dynamic getters that can throw exceptions.
Auditing your exposed API is likely to be quite difficult so we strongly recommend you update to a patched version of Electron.
Fixed Versions
25.0.0-alpha.224.0.123.2.322.3.6
For more information
If you have any questions or comments about this advisory, email us at security@electronjs.org
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | electron | < 22.3.6, >= 23.0.0-alpha.1, < 23.2.3, >= 24.0.0-alpha.1, < 24.0.1, >= 25.0.0-alpha.1, < 25.0.0-alpha.2 | 22.3.6, 23.2.3, 24.0.1, 25.0.0-alpha.2 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L- Weakness (CWE)
CWE-754- Platform
- npm
- Package
electron- Disclosed
- 06.09.2023
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-p7v2-p9m8-qqg7 - CC BY 4.0
Vulnerability history: electron
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 72
- First → latest
- 10.2017 10.2026
- Without a fix
- 0
- Exploited in attacks
- 3
Severity breakdown
- Critical 3
- High 26
- Medium 33
- Low 10
Disclosures per year
- 2017: 1
- 2018: 5
- 2019: 0
- 2020: 6
- 2021: 2
- 2022: 7
- 2023: 6
- 2024: 0
- 2025: 3
- 2026: 42
-
Electron context isolation bypass via nested unserializable return value this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.