CVE-2026-113800

Electron: HID and USB permission checks can be attributed to the wrong origin

Workarounds

Don't add allow="hid" / allow="usb" to untrusted iframes, or make the decision in your select-hid-device / select-usb-device handler using details.frame.

Fixed Versions

• 45.0.0-alpha.5
• 44.3.0
• 43.7.0
• 42.11.3

For more information

If you have any questions or comments about this advisory, email us at [email protected]

For hid and usb permission checks made from an iframe, session.setPermissionCheckHandler was given the top-level frame's origin and details instead of the requesting frame's. Apps that allow these permissions based on origin could grant an embedded frame access intended for the top-level page.

You're only affected if you use setPermissionCheckHandler with origin-based logic for hid or usb and embed cross-origin iframes with allow="hid" or allow="usb". Apps that don't delegate those features to untrusted iframes are not affected.

CVE-2026-113800 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (45.0.0-alpha.5, 44.3.0, 43.7.0, 42.11.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-113800? CVE-2026-113800 is a medium-severity security vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-alpha.5. It is fixed in 45.0.0-alpha.5, 44.3.0, 43.7.0, 42.11.3.
2. How severe is CVE-2026-113800? CVE-2026-113800 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2026-113800? electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.5 is affected.
4. Is there a fix for CVE-2026-113800? Yes. CVE-2026-113800 is fixed in 45.0.0-alpha.5, 44.3.0, 43.7.0, 42.11.3. Upgrade to this version or later.
5. Is CVE-2026-113800 exploitable, and should I be worried? Whether CVE-2026-113800 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-113800 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-113800?
   • Upgrade electron to 45.0.0-alpha.5 or later
   • Upgrade electron to 44.3.0 or later
   • Upgrade electron to 43.7.0 or later
   • Upgrade electron to 42.11.3 or later

Other vulnerabilities in electron