Electron up to 42.11.5/43.7.2/44.4.2/45.0.0-alpha.8 GPU Process webContents.beginFrameSubscription out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 2.67+ |
Summary
A vulnerability has been found in Electron up to 42.11.5/43.7.2/44.4.2/45.0.0-alpha.8 and classified as problematic. This vulnerability affects the function webContents.beginFrameSubscription of the component GPU Process. The manipulation leads to out-of-bounds.
This vulnerability is traded as CVE-2026-114122. An attack has to be approached locally. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Electron up to 42.11.5/43.7.2/44.4.2/45.0.0-alpha.8. It has been rated as problematic. This issue affects the function webContents.beginFrameSubscription of the component GPU Process. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.6, 43.7.3, 44.4.3, and 45.0.0-alpha.9, frame data received from the GPU process for webContents.beginFrameSubscription was not fully validated by the main process. An attacker who had separately gained code execution in the GPU process could supply inconsistent frame geometry and cause the main process to read out-of-bounds memory while producing captured frame images, disclosing memory or crashing the application. This issue is fixed in versions 42.11.6, 43.7.3, 44.4.3, and 45.0.0-alpha.9.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-114122 since 10/20/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 42.11.6, 43.7.3, 44.4.3 or 45.0.0-alpha.9 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 42.11.0
- 42.11.1
- 42.11.2
- 42.11.3
- 42.11.4
- 42.11.5
- 43.7.0
- 43.7.1
- 43.7.2
- 44.4.0
- 44.4.1
- 44.4.2
- 45.0.0-alpha.0
- 45.0.0-alpha.1
- 45.0.0-alpha.2
- 45.0.0-alpha.3
- 45.0.0-alpha.4
- 45.0.0-alpha.5
- 45.0.0-alpha.6
- 45.0.0-alpha.7
- 45.0.0-alpha.8
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.9
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: Out-of-boundsCWE: CWE-125 / CWE-119
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.11.6/43.7.3/44.4.3/45.0.0-alpha.9
Timeline
10/20/2026 CVE reserved10/21/2026 Advisory disclosed
10/21/2026 VulDB entry created
10/21/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-114122 (🔒)
GCVE (CVE): GCVE-0-2026-114122
GCVE (VulDB): GCVE-100-424889
Entry
Created: 10/21/2026 18:49Changes: 10/21/2026 18:49 (64)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.