LowGHSA-f37v-82c4-4x64CVE-2026-34781

Electron: Crash in clipboard.readImage() on malformed clipboard image data

Published 7 Apr 2026 · Updated 8 Apr 2026

Affected packages

electronnpm

Affected: <39.8.5
Fixed in: 39.8.5

Update to the fixed version for your release line, for example:npm install electron@39.8.5

electronnpm

Affected: >=40.0.0-alpha.1 <40.8.5
Fixed in: 40.8.5

Update to the fixed version for your release line, for example:npm install electron@40.8.5

electronnpm

Affected: >=41.0.0-alpha.1 <41.1.0
Fixed in: 41.1.0

Update to the fixed version for your release line, for example:npm install electron@41.1.0

electronnpm

Affected: >=42.0.0-alpha.1 <42.0.0-alpha.5
Fixed in: 42.0.0-alpha.5

Update to the fixed version for your release line, for example:npm install electron@42.0.0-alpha.5

Details

Impact

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.

Workarounds

Validate that the clipboard contains image data via clipboard.availableFormats() before calling clipboard.readImage(). Note this only narrows the window — upgrading to a fixed version is recommended.

Fixed Versions

42.0.0-alpha.5
41.1.0
40.8.5
39.8.5

For more information

If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org)

Is GHSA-f37v-82c4-4x64 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.