Electron up to 38.8.5/39.8.0/40.8.0/40.x Instance Message app.requestSingleInstanceLock out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Electron up to 38.8.5/39.8.0/40.8.0/40.x. The impacted element is the function app.requestSingleInstanceLock of the component Instance Message Handler. This manipulation causes out-of-bounds.
The identification of this vulnerability is CVE-2026-34776. The attack can only be executed locally. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Electron up to 38.8.5/39.8.0/40.8.0/40.x. It has been declared as critical. Affected by this vulnerability is the function app.requestSingleInstanceLock of the component Instance Message Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect 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 38.8.6, 39.8.1, 40.8.1, and 41.0.0, on macOS and Linux, apps that call app.requestSingleInstanceLock() were vulnerable to an out-of-bounds heap read when parsing a crafted second-instance message. Leaked memory could be delivered to the app's second-instance event handler. This issue is limited to processes running as the same user as the Electron app. Apps that do not call app.requestSingleInstanceLock() are not affected. Windows is not affected by this issue. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-34776 since 03/30/2026. The exploitation appears to be difficult. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 38.8.6, 39.8.1, 40.8.1 or 41.0.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 38.8.0
- 38.8.1
- 38.8.2
- 38.8.3
- 38.8.4
- 38.8.5
- 39.0
- 39.1
- 39.2
- 39.3
- 39.4
- 39.5
- 39.6
- 39.7
- 39.8.0
- 40.0
- 40.1
- 40.2
- 40.3
- 40.4
- 40.5
- 40.6
- 40.7
- 40.8.0
- 40.x
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
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
EPSS Score: 🔒
EPSS Percentile: 🔒
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 38.8.6/39.8.1/40.8.1/41.0.0
Timeline
03/30/2026 CVE reserved04/04/2026 Advisory disclosed
04/04/2026 VulDB entry created
04/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-3c8v-cfp5-9885
Status: Confirmed
CVE: CVE-2026-34776 (🔒)
GCVE (CVE): GCVE-0-2026-34776
GCVE (VulDB): GCVE-100-355219
Entry
Created: 04/04/2026 07:15Changes: 04/04/2026 07:15 (65)
Complete: 🔍
Cache ID: 216:16F: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.