Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS
Why It Matters
Analysis dossierWhy It Matters
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI enabled but corsEnabled disabled could remain script-readable across origins. This residual issue completes the remediation for CVE-2026-70604. Applications are affected only when they expose such a scheme and load untrusted content in the same session. Schemes intentionally registered with corsEnabled enabled remain cross-origin readable by design. This issue is fixed in versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5.
High
Unknown
Unknown
Risk basis: SOC ecosystem technology relevance; HIGH severity; Source severity; no confirmed exploitation signal
Affected Products & Remediation
1 source-backed product- electronjs electron · < 41.10.6; >= 42.0.0 < 42.9.2; >= 43.0.0 < 43.4.1; 44.0.0 · NVD CPE · Source
Vendor or catalog guidance (source)
Not provided by source
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- Unknown
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched user-interaction-client (CVSS AV:N, CVSS UI:R)
Exposure
- Identify endpoints reporting this CVE, especially those used for email and web browsing.Telemetry: DeviceTvmSoftwareVulnerabilities · A network vector that needs user interaction points at user-facing client software. · Rule user-interaction-client
Exploitation evidence
- Review unusual child processes started by the affected client application on affected endpoints.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule user-interaction-client
Response
- Confirm the source-stated update on affected endpoints.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies remediation. · Rule user-interaction-client
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- security-advisories@github.com
- Record status · verification
- UPDATED · NVD API
- CPE
- cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha1:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha2:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha3:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha4:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha5:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha6:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha7:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha8:*:*:*:node.js:*:*, cpe:2.3:a:electronjs:electron:44.0.0:alpha9:*:*:*:node.js:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-102675"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descLooking up related community queries…