GHSA-h3v5-h239-pg29 CVE-2026-114124

Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry

Low npm

Severity: 3.9 / 10; Low · CVSS 3.1
Exploit chance (EPSS): 0.18%; Chance of exploitation in the next 30 days. Higher than 8.16% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-125 Out-of-bounds Read
Fix: 42.11.6; Upgrade electron to this version or later

Description

Impact

In offscreen rendering mode on macOS, frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing paint event images, disclosing memory or crashing the app. GHSA-pfmc-3mgc-p6fp covers the same issue on the other capture paths.

Apps are only affected if they use offscreen rendering (webPreferences.offscreen) on macOS and an attacker has separately gained code execution in the GPU process. Apps that do not use offscreen rendering are not affected.

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

45.0.0-alpha.9
44.4.3
43.7.3
42.11.6

For more information

If you have any questions or comments about this advisory, email us at security@electronjs.org

Affected versions

npm

Package	Vulnerable	Fixed in
electron	`< 42.11.6`	`42.11.6`
electron	`>= 43.0.0-alpha.1, < 43.7.3`	`43.7.3`
electron	`>= 44.0.0-alpha.1, < 44.4.3`	`44.4.3`
electron	`>= 45.0.0-alpha.1, < 45.0.0-alpha.9`	`45.0.0-alpha.9`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

electron npm → `42.11.6`

npm

npm install electron@42.11.6

yarn

yarn add electron@42.11.6

pnpm

pnpm add electron@42.11.6

Severity breakdown

CVSS 3.1 3.9

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L

Attack vector: Local
Attack complexity: High
Privileges required: High
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: Low

Weakness

CWE-125: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How to prevent it

Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.
Architecture and Design: Use a language that provides appropriate memory abstractions.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-114124

Packages

github.com/electron/electron

Timeline

Oct 21, 2026 Published
Oct 23, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-qqvq-6xgj-jw8g Electron affected by libvpx's heap buffer overflow in vp8 encoding	High Known exploited	Also affects electron
GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable	High Known exploited	Also affects electron
GHSA-995f-9x5r-2rcj Heap buffer overflow in GPU	Critical Known exploited	Also affects electron
GHSA-jr5w-w6x2-84p9 Electron: Mitigation for compromised eMudhra intermediate certificates	High	Also affects electron
GHSA-3qxv-5xgr-q7w9 Electron: Frame subscription trusts GPU-supplied frame geometry	Low	Also affects electron
GHSA-997q-gvvc-jwmx Electron: openExternal permission requests can be attributed to the wrong origin	Medium	Also affects electron
GHSA-fw47-9c62-h3vw Electron: HID and USB permission checks can be attributed to the wrong origin	Medium	Also affects electron
GHSA-x562-297c-g43g Electron: Pointer lock permission requests can be attributed to the wrong frame	Medium	Also affects electron

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor