CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NHigh (7.4) in electronjs electron. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in electron 41.10.6, 42.9.2, 43.4.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:Nelectron (npm): fixed in 41.10.6, 42.9.2, 43.4.1, 44.0.0-beta.5Explain CVE-2026-102675 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102675?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102675?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102675 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| electronjs:electron | before 41.10.6 |
| electronjs:electron | from 42.0.0 before 42.9.2 |
| electronjs:electron | from 43.0.0 before 43.4.1 |
| electronjs:electron | 44.0.0:alpha1 |
| electronjs:electron | 44.0.0:alpha2 |
| electronjs:electron | 44.0.0:alpha3 |
| electronjs:electron | 44.0.0:alpha4 |
| electronjs:electron | 44.0.0:alpha5 |
| electronjs:electron | 44.0.0:alpha6 |
| electronjs:electron | 44.0.0:alpha7 |
| electronjs:electron | 44.0.0:alpha8 |
| electronjs:electron | 44.0.0:alpha9 |
| electronjs:electron | 44.0.0:beta1 |
| electronjs:electron | 44.0.0:beta2 |
| electronjs:electron | 44.0.0:beta3 |
| electronjs:electron | 44.0.0:beta4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-j84w-jfhq-vhvj | npm | electron | <41.10.6 | 41.10.6 |
| GHSA-j84w-jfhq-vhvj | npm | electron | >=42.0.0-alpha.1 <42.9.2 | 42.9.2 |
| GHSA-j84w-jfhq-vhvj | npm | electron | >=43.0.0-alpha.1 <43.4.1 | 43.4.1 |
| GHSA-j84w-jfhq-vhvj | npm | electron | >=44.0.0-alpha.1 <44.0.0-beta.5 | 44.0.0-beta.5 |
Red Hat rates this Important.
A flaw was found in Electron where responses served via protocol.registerFileProtocol or protocol.registerHttpProtocol for custom schemes registered with supportFetchAPI enabled but corsEnabled disabled remain script-readable across origins. If untrusted content is loaded within the same session, an attacker can exploit this behavior to bypass the same-origin policy and read sensitive application data, resulting in information disclosure.
Ensure custom schemes registered with supportFetchAPI explicitly enable corsEnabled, or avoid loading untrusted web content within sessions where custom protocol schemes with disabled CORS controls are registered.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Build of Podman Desktop | rh-podman-desktop | Affected | |
| Red Hat Enterprise Linux 10 | podman-desktop | Affected | |
| Red Hat Enterprise Linux 10 | rh-podman-desktop | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102675.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-346 (16).