CVE-2026-34781
2.8 · LOWOverview
CVE-2026-34781 is a low-severity vulnerability affecting electronjs electron. It was published on April 7, 2026 and has a CVSS 3.1 base score of 2.8 (LOW).
This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical Description
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.
Remediation
Check the references section for vendor advisories and patches from electronjs. Update electron to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| electronjs | electron | 0 | Affected |
Frequently Asked Questions
What is CVE-2026-34781?
CVE-2026-34781 is a low-severity vulnerability affecting electronjs electron. It was published on April 7, 2026 and has a CVSS 3.1 base score of 2.8 (LOW).
How severe is CVE-2026-34781?
This vulnerability has a CVSS 3.1 base score of 2.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2026-34781?
Check the references section for vendor advisories and patches from electronjs. Update electron to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2026-34781?
CyberStrike's AI-powered security agents can automatically detect CVE-2026-34781 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2026
View all →Improper handling of values in the microcode flow for some Intel(R) Processor Family may allow an es
A flaw was found in libsoup, a library used by applications to send network requests. This vulnerabi
A flaw was found in libsoup. A remote attacker, by controlling the method parameter of the `soup_mes
A flaw was found in libsoup. An attacker controlling the value used to set the Content-Type header c
OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, feeding a crafted
OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, sc_compacttlv_fin
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and C
HCL BigFix Service Management (SM) is susceptible to a Root File System Not Mounted as Read-Only. An
FacturaScripts is an open source accounting and invoicing software. Versions 2025.7 and prior contai
An integer underflow in the volxlate function in Netatalk 3.0.0 through 4.4.2 allows a local privile
Capsule is a multi-tenancy and policy-based framework for Kubernetes. To defend against namespace hi
Improper input validation in Microsoft Azure Attestation service and Device Health Attestation Servi