Quick answers
- Is CVE-2026-113800 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113800 being exploited in the wild.
- How severe is CVE-2026-113800?
- Medium severity, with a CVSS score of 5.4, published 21 October 2026.
- Which products and versions are affected?
- Electron before 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5; electron (npm) >= 45.0.0-alpha.1, < 45.0.0-alpha.5, SEMVER:introduced=45.0.0-alpha.1,fixed=45.0.0-alpha.5.
- Is there a fix for CVE-2026-113800?
- Yes. electron (npm): upgrade to 45.0.0-alpha.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113800 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113800?
- Check whether you run Electron or electron (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- electron (npm): upgrade to 45.0.0-alpha.5 or later
npm install electron@45.0.0-alpha.5
Technical details
The vulnerability exists in the HID and USB permission check handlers, which incorrectly report the top-level frame's origin instead of the requesting iframe's origin to the application's permission check callback. This causes origin-based permission logic to be bypassed when the request originates from a cross-origin iframe. An attacker can exploit this by embedding malicious content in an iframe on a trusted page and gaining unauthorized access to hardware devices. The fix ensures the requesting frame's origin is properly reported in all permission checks.
Affected products
- Electron Electron before 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5
Identifiers
- CVE-2026-113800
- GHSA-fw47-9c62-h3vw
Timeline
- 2026-10-21: disclosed
- 2026-09-07: patched