Electron up to 42.9.x/43.4.x/44.0.0-beta.5 Sandboxed Preload Code Cache input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 1.77- |
Summary
A vulnerability identified as problematic has been detected in Electron up to 42.9.x/43.4.x/44.0.0-beta.5. This impacts an unknown function of the component Sandboxed Preload Code Cache. Performing a manipulation results in input validation. This vulnerability is identified as CVE-2026-102677. The attack is only possible with local access. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Electron up to 42.9.x/43.4.x/44.0.0-beta.5. This affects some unknown functionality of the component Sandboxed Preload Code Cache. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-102677 since 09/29/2026. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 42.10.0, 43.5.0 or 44.0.0-beta.6 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 42.0
- 42.1
- 42.2
- 42.3
- 42.4
- 42.5
- 42.6
- 42.7
- 42.8
- 42.9
- 43.0
- 43.1
- 43.2
- 43.3
- 43.4
- 44.0.0-beta.0
- 44.0.0-beta.1
- 44.0.0-beta.2
- 44.0.0-beta.3
- 44.0.0-beta.4
- 44.0.0-beta.5
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Electron 42.10.0/43.5.0/44.0.0-beta.6
Timeline
09/29/2026 Advisory disclosed09/29/2026 CVE reserved
09/29/2026 VulDB entry created
09/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-102677 (🔒)
GCVE (CVE): GCVE-0-2026-102677
GCVE (VulDB): GCVE-100-411651
Entry
Created: 09/29/2026 20:40Changes: 09/29/2026 20:40 (63)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.