CVE-2022-4135 is a critical-severity (CVSS 9.6) Out-of-bounds Write vulnerability in electron. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-11-28) — treat it as actively exploited and patch now. A fix is available for electron — see the affected versions and patch details below.
Heap buffer overflow in GPU
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-11-28. Federal agencies were required to remediate by 2022-12-19.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-4135.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-4135 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
electronnpmDescription
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | electron | ≥ 19.0.0&&< 19.1.8 | 19.1.8npm install electron@19.1.8 |
Affected Products
chromegoogleedgemicrosoftedge chromiummicrosoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 all…
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 all…
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 all…
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 all…
Detection & mitigation playbook
Open-source dependencyDetect
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 19.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4135 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is CVE-2022-4135 in your dependencies?
Find it across npm, including transitive dependencies.