How severe is CVE-2026-114122?

CVE-2026-114122 has a CVSS score of 3.9/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-114122?

CVE-2026-114122 affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix CVE-2026-114122?

Update electron to 42.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-114122 is resolved across your whole dependency graph.

How do I detect CVE-2026-114122 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-114122 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is CVE-2026-114122 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-114122 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-114122?

CVE-2026-114122 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-114122?

CVE-2026-114122 is classified as Out-of-bounds Read (CWE-125). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-114122 published, and has it been updated?

CVE-2026-114122 was published on October 21, 2026 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

CVE-2026-114122 — electron

LOWFix: electron/electron@24d8dbc

CVE-2026-114122 is a low-severity (CVSS 3.9) Out-of-bounds Read vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: Frame subscription trusts GPU-supplied frame geometry

Also known asGHSA-3qxv-5xgr-q7w9

Published

Oct 21, 2026

Updated

Oct 22, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-114122 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

electronnpm

5.3Mdownloads / week

Description

Impact

Frame data received from the GPU process for webContents.beginFrameSubscription 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 the captured frame images, disclosing memory or crashing the app.

Apps are only affected if they use webContents.beginFrameSubscription and an attacker has separately gained code execution in the GPU process. Apps that do not subscribe to captured frames 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 [email protected]

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	42.11.6`npm install electron@42.11.6`
📦npm	`electron`	≥ 43.0.0-alpha.1&&< 43.7.3	43.7.3`npm install electron@43.7.3`
📦npm	`electron`	≥ 44.0.0-alpha.1&&< 44.4.3	44.4.3`npm install electron@44.4.3`
📦npm	`electron`	≥ 45.0.0-alpha.1&&< 45.0.0-alpha.9	45.0.0-alpha.9`npm install electron@45.0.0-alpha.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 42.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-114122 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

### Impact Frame data received from the GPU process for `webContents.beginFrameSubscription` 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 the captured frame images, disclosing memory or crashing the app. Apps are only affected if they use `webContents.beginFrameSubscription` and an attacker has separately gained code execution in the GPU process. Apps that do not subscribe to captured frames are not affected. ### Workarounds There are no app side workarounds, you must update to a patched versi