CVE Intelligence
Medium

CVE-2026-113798 — Electron: Pointer lock permission requests can be attributed to the wrong frame

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.

Published Oct 21, 2026 · Updated Oct 27, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.24%
ahead of 16% of scored CVEs · Oct 29, 2026
Affects
Electron
Electron
CVSS base
5.4
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm Electron: fixed in version 45.0.0-alpha.13 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 44.5.0 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 43.7.6 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 42.11.9 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Electron Electron, Npm Electron).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Electron Electron version < 42.11.9version >= 43.0.0-alpha.1, < 43.7.6version >= 44.0.0-alpha.1, < 44.5.0version >= 45.0.0-alpha.1, < 45.0.0-alpha.13 Vulnerable CVE Program (cve.org) e CISA ADP
Npm Electron ≥ 45.0.0-alpha.1 and < 45.0.0-alpha.13≥ 44.0.0-alpha.1 and < 44.5.0≥ 43.0.0-alpha.1 and < 43.7.6< 42.11.9 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.4 CVSS 3.1 Medium 2.8 2.5 security-advisories@github.com via NIST National Vulnerability Database
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.4 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-346

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 29, 2026 · 8 reading(s) · max 0.24%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Awaiting Analysis → Undergoing Analysis
    Oct 24, 2026 · NIST National Vulnerability Database
  • Fix documented
    Oct 22, 2026 · GitHub Security Advisories
  • Affected products added · npm/electron
    Oct 22, 2026 · GitHub Security Advisories
  • Source status changed · Received → Awaiting Analysis
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products added · electron/electron
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • CVSS changed · 5.4
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

17 on the record

Elsewhere on this site

Electron
every CVE for this vendor
CWE-346
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-115570 Electron: Mitigation for compromised eMudhra intermediate certificates 6d
  • CVE-2026-114124 Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry 8d
  • CVE-2026-114121 Electron: openExternal permission requests can be attributed to the wrong origin 8d
  • CVE-2026-114122 Electron: Frame subscription trusts GPU-supplied frame geometry 8d
  • CVE-2026-113800 Electron: HID and USB permission checks can be attributed to the wrong origin 8d
  • CVE-2026-113796 Electron: SameSite cookie restrictions are not applied to windows opened from links 8d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-113798 is "Electron: Pointer lock permission requests can be attributed to the wrong frame", rated Medium. It affects Electron (Electron); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.