| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qmv3-fv6v-rmhq | Electron: Sandboxed preload code cache can be poisoned by a compromised renderer |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 02 Oct 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 01 Oct 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-829 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 29 Sep 2026 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Electron
Electron electron |
|
| Vendors & Products |
Electron
Electron electron |
Tue, 29 Sep 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Electron: Sandboxed preload code cache can be poisoned by a compromised renderer | |
| Weaknesses | CWE-20 CWE-345 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-02T12:18:18.477Z
Reserved: 2026-09-29T16:10:04.075Z
Link: CVE-2026-102677
Updated: 2026-10-02T12:18:14.080Z
Status : Undergoing Analysis
Published: 2026-09-29T18:17:09.573
Modified: 2026-10-02T13:17:19.563
Link: CVE-2026-102677
OpenCVE Enrichment
Updated: 2026-10-01T03:45:17Z
Github GHSA