CVE-2026-34781: Electron crashes in clipboard.readImage() on malformed clipboard image data
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: electron electron 39.8.5.
Low priority for now. Upgrade to electron electron 39.8.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, apps that call clipboard.readImage() may be vulnerable to a denial of service. If the system clipboard contains image data that fails to decode, the resulting null bitmap is passed unchecked to image construction, triggering a controlled abort and crashing the process. Apps are only affected if they call clipboard.readImage(). Apps that do not read images from the clipboard are not affected. This issue does not allow memory corruption or code execution. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.
- Published
- Apr 7, 2026
- Updated
- Jul 24, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-476
Report tools
Action score
13
Monitor
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.3
- CNA · GitHub_M
- 2.8
- 0.5 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| electronjs | electron | cpe:2.3:a:electronjs:electron |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- electronjs electronup to 39.8.4 inclusive
- electronjs electron40.0.0 and later · up to 40.8.4 inclusive
- electronjs electron41.0.0 and later · before 41.1.0
- electronjs electron41.2.0
- electronjs electron42.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
electron electron
- < 39.8.5, >= 40.0.0-alpha.1, < 40.8.5, >= 41.0.0-alpha.1, < 41.1.0, >= 42.0.0-alpha.1, < 42.0.0-alpha.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | electron | from 40.0.0-alpha.1 · before 40.8.5 | 40.8.5 |
| npm | electron | from 41.0.0-alpha.1 · before 41.1.0 | 41.1.0 |
| npm | electron | from 42.0.0-alpha.1 · before 42.0.0-alpha.5 | 42.0.0-alpha.5 |
| npm | electron | before 39.8.5 | 39.8.5 |
Same product
electronjs: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-16151Based on details posted by the ElectronJS team; A remote code execution vulnerability has been discovered in Google Chromium that affects al40Plan
- CVE-2026-102676Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions39Monitor
- CVE-2026-34775Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-34764Apr 6, 2026 · Electron has a use-after-free in offscreen shared texture release() callback22Monitor
- ← EarlierCVE-2026-34765Apr 7, 2026 · Electron named window.open targets not scoped to the opener's browsing context35Monitor
- Later →CVE-2026-70597Aug 5, 2026 · Electron: Parent process code-sign check is spoofable25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| electron electron | 39.8.5 · description | Vendor (CNA) |
| npm:electron | 39.8.5 | Package registry (OSV) |
| npm:electron | 40.8.5 | Package registry (OSV) |
| npm:electron | 41.1.0 | Package registry (OSV) |
| npm:electron | 42.0.0-alpha.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.