Approved changes feed: RSS · Atom

cpe:2.3:a:electronjs:electron:42.0.0:alpha4:*:*:*:node.js:*:*

part: a version: 42.0.0 update: alpha4

VendorElectronjs (2af93ff4-38f6-5aef-acc5-80ca92aa0b83)
ProductElectron (3ffe6bdf-afda-502c-ac98-8ec4a42261cc)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/electron/electron purl2cpe 2026-06-01 10:17:08.322383
pkg:gitlab/immersaview/electron purl2cpe 2026-06-01 10:17:08.322384
pkg:npm/electron purl2cpe 2026-06-01 10:17:08.322385
pkg:sourceforge/electron.mirror purl2cpe 2026-06-01 10:17:08.322387

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-34781 vulnerable 2026-06-08 07:59:13.140259 Electron crashes in clipboard.readImage() on malformed clipboard image data
LOW (2.8)
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: 2026-04-07T21:20:12.517Z
Updated: 2026-04-08T16:14:38.564Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-34765 vulnerable 2026-06-08 07:59:13.089474 Electron named window.open targets not scoped to the opener's browsing context
MEDIUM (6)
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, when a renderer calls window.open() with a target name, Electron did not correctly scope the named-window lookup to the opener's browsing context group. A renderer could navigate an existing child window that was opened by a different, unrelated renderer if both used the same target name. If that existing child was created with more permissive webPreferences (via setWindowOpenHandler's overrideBrowserWindowOptions), content loaded by the second renderer inherits those permissions. Apps are only affected if they open multiple top-level windows with differing trust levels and use setWindowOpenHandler to grant child windows elevated webPreferences such as a privileged preload script. Apps that do not elevate child window privileges, or that use a single top-level window, are not affected. Apps that additionally grant nodeIntegration: true or sandbox: false to child windows (contrary to the security recommendations) may be exposed to arbitrary code execution. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.
Published: 2026-04-07T21:18:35.375Z
Updated: 2026-04-13T15:37:12.686Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-34764 vulnerable 2026-06-08 07:59:13.087529 Electron has a use-after-free in offscreen shared texture release() callback
LOW (2.3)
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 33.0.0-alpha.1 to before 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, apps that use offscreen rendering with GPU shared textures may be vulnerable to a use-after-free. Under certain conditions, the release() callback provided on a paint event texture can outlive its backing native state, and invoking it after that point dereferences freed memory in the main process, which may lead to a crash or memory corruption. Apps are only affected if they use offscreen rendering with webPreferences.offscreen: { useSharedTexture: true }. Apps that do not enable shared-texture offscreen rendering are not affected. To mitigate this issue, ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5.
Published: 2026-04-06T15:46:40.189Z
Updated: 2026-04-07T16:00:32.633Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.