← Back to results
Vulnerability record · public intelligence
CVE-2026-70612
MEDIUM

Electron: Sandboxed iframes can launch external protocol handlers

Published Aug 5, 2026 · Updated Oct 23, 2026 · Also known as GHSA-p2rr-rvmm-c5fp

Severity · CVSSMEDIUM · 5.4
Known exploitationNot listed
EPSS / likelihood0.43%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Electron: Sandboxed iframes can launch external protocol handlers

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame's sandbox state was also not made available to the app's permission handlers.

Potential impact

Requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame's sandbox state was also not made available to the app's permission handlers. Apps are only affected if they render untrusted content in sandboxed iframes and grant the openExternal permission (granted by default when no setPermissionRequestHandler is installed). Apps whose permission handler denies openExternal for untrusted content are not affected.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-p2rr-rvmm-c5fp

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Source repository ↗
  5. Source repository ↗
  6. Patch commit ↗
  7. Patch commit ↗
  8. Patch commit ↗
  9. Patch commit ↗
  10. Source repository ↗
  11. Source repository ↗
  12. Source repository ↗

Record history

Published Aug 5, 2026 · Last refreshed Oct 23, 2026