CVE-2026-113800 electron CVE debrief

Who should care

Developers and security teams responsible for Electron applications that use HID or USB permissions and embed cross-origin iframes should assess their exposure and update to fixed versions or adjust their logic accordingly.

Why it matters

CVE-2026-113800 allows unintended access to Electron applications using HID or USB permissions. Assess exposure, update to fixed versions, and adjust logic to prevent exploitation.

• Assess and update Electron applications to fixed versions to prevent unintended access.
• Review and adjust origin-based logic for HID and USB permissions.
• Avoid adding allow='hid' or allow='usb' to untrusted iframes to limit exposure.

Technical summary

In Electron, HID and USB permission checks made from an iframe were incorrectly attributed to the top-level frame's origin and details instead of the requesting frame's. This could allow apps that use setPermissionCheckHandler with origin-based logic for HID or USB and embed cross-origin iframes with allow='hid' or allow='usb' to grant unintended access. The vulnerability affects Electron applications that use HID or USB permissions and embed cross-origin iframes. Developers should review and adjust their origin-based logic for HID and USB permissions.

Defensive priority

Assess exposure in Electron applications using setPermissionCheckHandler with origin-based logic for HID or USB and embedding cross-origin iframes with allow='hid' or allow='usb'.

Recommended defensive actions

• Assess and update Electron applications to use fixed versions: 45.0.0-alpha.5, 44.3.0, 43.7.0, or 42.11.3.
• Review and adjust origin-based logic for HID and USB permissions in setPermissionCheckHandler.
• Avoid adding allow='hid' or allow='usb' to untrusted iframes.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The source corpus provides details on the vulnerability and affected versions. Evidence of exploitation is not provided, but developers should verify their applications' exposure and update to fixed versions. The vulnerability is attributed to incorrect origin and details being used in permission checks. Limited evidence is available, and defenders should review the official advisory and CVE record for more information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.