Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Context isolation bypass in ElectronGHSA-56pc-6jqp-xqj8

MEDIUM

GHSA-56pc-6jqp-xqj8 is a medium-severity (CVSS 5.6) CWE-668 vulnerability in electron. 1 public exploit reference exists, so weaponization risk is real. A fix is available for electron — see the affected versions and patch details below.

Also known asCVE-2020-15215
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.00%0.39%0.79%1.18%0.3%0.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-56pc-6jqp-xqj8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 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
7.7Mdownloads / week

Description

Impact

Apps using both contextIsolation and sandbox: true are affected. Apps using both contextIsolation and nativeWindowOpen: true are affected.

This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions.

Workarounds

There are no app-side workarounds, you must update your Electron version to be protected.

Fixed Versions

  • 11.0.0-beta.6
  • 10.1.2
  • 9.3.1
  • 8.5.2

For more information

If you have any questions or comments about this advisory:

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectron≥ 8.0.0-beta.0&&< 8.5.28.5.2npm install electron@8.5.2
📦npmelectron≥ 9.0.0-beta.0&&< 9.3.19.3.1npm install electron@9.3.1
📦npmelectron≥ 10.0.0-beta.0&&< 10.1.210.1.2npm install electron@10.1.2
📦npmelectron≥ 11.0.0-beta.0&&< 11.0.0-beta.611.0.0-beta.6npm install electron@11.0.0-beta.6

Affected Products

1 product · 100 configurations
Application
electronelectronjs
39 versions
8.0.08.0.18.0.28.0.38.1.08.1.18.2.08.2.18.2.28.2.38.2.48.2.5
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

NishantIyer/CVE-2020-15215-Discord-POC

⭐ 16🍴 14May 2026

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

    Update electron to 8.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56pc-6jqp-xqj8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Apps using both `contextIsolation` and `sandbox: true` are affected. Apps using both `contextIsolation` and `nativeWindowOpen: true` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. ### Workarounds There are no app-side workarounds, you must update your Electron version to be protected. ### Fixed Versions * `11.0.0-beta.6` * `10.1.2` * `9.3.1` * `8.5.2` ### For more information If you have any questions or comments about this advisory:
O3 Security · Impact-Aware SCA

Is GHSA-56pc-6jqp-xqj8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Context isolation bypass in Electron (Medium 5.6)