Skip to content
Noroxi
CVE-2020-15096· NVD / CVE Program· CNA GitHub_M

Context isolation bypass via Promise in Electron

In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there 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. Apps using "contextIsolation" are affected. There are no app-side workarounds, you must update your Electron version to be protected. This is fixed in versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21.

MediumCVSS 6.8 · v3.1—No exploit Fix available
Published
Jul 6, 2020
Updated
Jun 16, 2026
EPSS
0.8% · 55th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CNA vs NVD score

NVD
6.8
CNA · GitHub_M
6.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
electronjselectron

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • electronjs electronbefore 6.1.1
  • electronjs electron7.0.0 and later · before 7.2.4
  • electronjs electron8.0.0 and later · before 8.2.4
  • electronjs electron9.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • electron electron

    • < 6.1.1, >= 7.0.0, < 7.2.4, >= 8.0.0, < 8.2.4, >=9.0.0-beta.0, < 9.0.0-beta.21affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmelectronfrom 7.0.0 · before 7.2.47.2.4
npmelectronfrom 8.0.0 · before 8.2.48.2.4
npmelectronbefore 6.1.116.1.11

Same product

electronjs: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-16151Based on details posted by the ElectronJS team; A remote code execution vulnerability has been discovered in Google Chromium that affects al
    40Plan
  • CVE-2026-34775Electron: nodeIntegrationInWorker not correctly scoped in shared renderer processes
    39Monitor
  • CVE-2023-23623Content-Secrity-Policy disabling eval not applied consistently in renderers with sandbox disabled in Electron
    39Monitor
  • CVE-2022-29247Exposure of Resource to Wrong Sphere in Electron
    39Monitor
  • CVE-2020-4077Context isolation bypass via contextBridge in Electron
    39Monitor
  • CVE-2020-4076Context isolation bypass via leaked cross-context objects in Electron
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:electron6.1.11Package registry (OSV)
npm:electron7.2.4Package registry (OSV)
npm:electron8.2.4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-501 · Trust Boundary Violation

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records