GHSA-j84w-jfhq-vhvj CVE-2026-102675
Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled
- Severity
- 7.4 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.21%
- Chance of exploitation in the next 30 days. Higher than 11.75% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-346 Origin Validation Error
- Fix
41.10.6- Upgrade electron to this version or later
Description
Impact
Responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI: true but without corsEnabled: true could be read cross-origin by web content. This completes the fix for CVE-2026-70604.
Apps are only affected if they register such a scheme, serve it through one of those handlers, and load untrusted content. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.
Workarounds
Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
Fixed Versions
44.0.0-beta.543.4.142.9.241.10.6
For more information
If you have any questions or comments about this advisory, email us at security@electronjs.org
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| electron | < 41.10.6 |
41.10.6 |
| electron | >= 42.0.0-alpha.1, < 42.9.2 |
42.9.2 |
| electron | >= 43.0.0-alpha.1, < 43.4.1 |
43.4.1 |
| electron | >= 44.0.0-alpha.1, < 44.0.0-beta.5 |
44.0.0-beta.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
electron npm → 41.10.6
- npm
npm install electron@41.10.6- yarn
yarn add electron@41.10.6- pnpm
pnpm add electron@41.10.6
Severity breakdown
CVSS 3.1 7.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-346: Origin Validation Error
The product does not properly verify that the source of data or communication is valid.
References
Packages
Other links
- github.com/electron/electron/security/advisories/GHSA-j84w-jfhq-vhvj
- github.com/electron/electron/commit/4d2784cc8592471ee2276235b8c2a03efddf937d
- github.com/electron/electron/commit/80178e4631cb2f6a5e42f8e793b2ae9624e78a0d
- github.com/electron/electron/commit/c595b05976e7a885465b043d17e00a92fc3c3397
- github.com/electron/electron/commit/ef75c4b98caaa3ebc615f1eba302027028ee04d2
- github.com/electron/electron/releases/tag/v41.10.6
- github.com/electron/electron/releases/tag/v42.9.2
- github.com/electron/electron/releases/tag/v43.4.1
- github.com/electron/electron/releases/tag/v44.0.0-beta.5
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-qqvq-6xgj-jw8g Electron affected by libvpx's heap buffer overflow in vp8 encoding | High Known exploited | Also affects electron |
| GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable | High Known exploited | Also affects electron |
| GHSA-995f-9x5r-2rcj Heap buffer overflow in GPU | Critical Known exploited | Also affects electron |
| GHSA-jr5w-w6x2-84p9 Electron: Mitigation for compromised eMudhra intermediate certificates | High | Also affects electron |
| GHSA-h3v5-h239-pg29 Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry | Low | Also affects electron |
| GHSA-3qxv-5xgr-q7w9 Electron: Frame subscription trusts GPU-supplied frame geometry | Low | Also affects electron |
| GHSA-997q-gvvc-jwmx Electron: openExternal permission requests can be attributed to the wrong origin | Medium | Also affects electron |
| GHSA-fw47-9c62-h3vw Electron: HID and USB permission checks can be attributed to the wrong origin | Medium | Also affects electron |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor