HighCVE-2026-70608

    Electron: Sandboxed iframe can bypass the allow-popups restriction via the OpenURL navigation path (CVE-2026-70608)

    Published Last modified Sources: OSV, CVE.org

    Share

    What is affected, what to do

    Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 41.10.3, and 42.0.1, a sandboxed iframe without the allow-popups keyword could still open a new window or trigger setWindowOpenHandler with no user interaction because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction.

    Update Electron to version 39.8.10.

    Affected
    • Electron gte 40.0.0-alpha.1, < 41.10.3..*
    • Electron lt *..39.8.10
    Fixed in
    • Electron 39.8.10

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.2

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: OSV, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 37.3

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    69.17 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.2 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    37.3
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 5 August 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-693, CWE-1021

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 41.10.3, and 42.0.1, a sandboxed iframe without the allow-popups keyword could still open a new window or trigger setWindowOpenHandler with no user interaction because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction. Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected, while apps that deny window creation in setWindowOpenHandler or do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in 39.8.10, 41.10.3, and 42.0.1.

    Source: OSV (Open Source Vulnerabilities), NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    electronelectron
    • ≥ 40.0.0-alpha.1, < 41.10.3
    • < 39.8.10
    • —
    • 39.8.10
    electronjselectron
    • 40.0.0 – < 41.10.3
    • < 39.8.8
    • 42.0.0 – < 42.0.1
    • 41.10.3
    • 39.8.8
    • 42.0.1

    Vendors and products

    Weakness classes (CWE)

    • CWE-693Protection Mechanism Failure

      Pillar

      The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

      Entry at MITRE CWE-693

    • CWE-1021Improper Restriction of Rendered UI Layers or Frames

      Base

      The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.

      Entry at MITRE CWE-1021

    References & sources

    • github.comelectron/electron/security/advisories/GHSA-9f4c-93c8-jc8gweb, x_refsource_CONFIRM
    • github.comelectron/electron/pull/51437web, x_refsource_MISC
    • github.comelectron/electron/pull/51438web, x_refsource_MISC
    • github.comelectron/electron/pull/51439web, x_refsource_MISC
    • github.comelectron/electron/commit/3ff23c52ab364a0afc6ab5bd7851291d3159de…web, x_refsource_MISC
    • github.comelectron/electron/commit/57cbe329c4ae8aab5ac5ebdcb588adc9a11de0…web, x_refsource_MISC
    • github.comelectron/electron/commit/68cf8b7d9122260f6b534a69a82c701a56cf15…web, x_refsource_MISC
    • github.comelectron/electronpackage
    • github.comelectron/electron/releases/tag/v39.8.10web, x_refsource_MISC
    • github.comelectron/electron/releases/tag/v41.10.3web, x_refsource_MISC
    • github.comelectron/electron/releases/tag/v42.0.1web, x_refsource_MISC

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Initial analysis by NVDNVD

      Newly listed as affected:
      Show 11 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* versions up to (excluding) 39.8.8 *cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* versions from (including) 40.0.0 up to (excluding) 41.10.3 *cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* versions from (including) 42.0.0 up to (excluding) 42.0.1
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/commit/3ff23c52ab364a0afc6ab5bd7851291d3159de57 Types: Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/commit/57cbe329c4ae8aab5ac5ebdcb588adc9a11de0d3 Types: Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/commit/68cf8b7d9122260f6b534a69a82c701a56cf159f Types: Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/pull/51437 Types: Issue Tracking, Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/pull/51438 Types: Issue Tracking, Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/pull/51439 Types: Issue Tracking, Patch
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/releases/tag/v39.8.10 Types: Release Notes
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/releases/tag/v41.10.3 Types: Release Notes
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/releases/tag/v42.0.1 Types: Release Notes
      Reference typeadded
      —
      GitHub, Inc.: https://github.com/electron/electron/security/advisories/GHSA-9f4c-93c8-jc8g Types: Vendor Advisory

      Source identifier: nvd@nist.gov

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-70608","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-08-05T18:14:00.193334Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. ReceivedGitHub

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

      Weakness type: CWE-693, CWE-1021

      Description added or changed

      Show 15 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      electron
      Descriptionadded
      —
      Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 41.10.3, and 42.0.1, a sandboxed iframe without the allow-popups keyword could still open a new window or trigger setWindowOpenHandler with no user interaction because new-window navigations taking the OpenURL path did not apply the iframe sandbox popup restriction. Apps that embed untrusted content in sandboxed iframes and rely on the absence of allow-popups to prevent window creation are affected, while apps that deny window creation in setWindowOpenHandler or do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in 39.8.10, 41.10.3, and 42.0.1.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
      Weakness type (CWE)added
      —
      CWE-693
      Weakness type (CWE)added
      —
      CWE-1021
      Referenceadded
      —
      https://github.com/electron/electron/commit/3ff23c52ab364a0afc6ab5bd7851291d3159de57
      Referenceadded
      —
      https://github.com/electron/electron/commit/57cbe329c4ae8aab5ac5ebdcb588adc9a11de0d3
      Referenceadded
      —
      https://github.com/electron/electron/commit/68cf8b7d9122260f6b534a69a82c701a56cf159f
      Referenceadded
      —
      https://github.com/electron/electron/pull/51437
      Referenceadded
      —
      https://github.com/electron/electron/pull/51438
      Referenceadded
      —
      https://github.com/electron/electron/pull/51439
      Referenceadded
      —
      https://github.com/electron/electron/releases/tag/v39.8.10
      Referenceadded
      —
      https://github.com/electron/electron/releases/tag/v41.10.3
      Referenceadded
      —
      https://github.com/electron/electron/releases/tag/v42.0.1
      Referenceadded
      —
      https://github.com/electron/electron/security/advisories/GHSA-9f4c-93c8-jc8g

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-70608
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-70608"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-70608.svg?lang=en" alt="CVE-2026-70608 – NEOSEC Intel" height="20"></a>