CVE-2026-34766

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

• 41.0.0-beta.8
• 40.7.0
• 39.8.0
• 38.8.6

For more information

If there are any questions or comments about this advisory, send an email to [email protected]

The select-usb-device event callback did not validate the chosen device ID against the filtered list that was presented to the handler. An app whose handler could be influenced to select a device ID outside the filtered set would grant access to a device that did not match the renderer's requested filters or was listed in exclusionFilters.

The WebUSB security blocklist remained enforced regardless, so security-sensitive devices on the blocklist were not affected. The practical impact is limited to apps with unusual device-selection logic.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-34766 has a CVSS score of 3.3 (Low). The vector is requires local access, low privileges required, and user interaction required. 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 (38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-34766? CVE-2026-34766 is a low-severity missing authorization vulnerability in electron (npm), affecting versions < 38.8.6. It is fixed in 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-34766? CVE-2026-34766 has a CVSS score of 3.3 (Low). 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-34766? electron (npm) versions < 38.8.6 is affected.
4. Is there a fix for CVE-2026-34766? Yes. CVE-2026-34766 is fixed in 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8. Upgrade to this version or later.
5. Is CVE-2026-34766 exploitable, and should I be worried? Whether CVE-2026-34766 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-34766 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-34766?
   • Upgrade electron to 38.8.6 or later
   • Upgrade electron to 39.8.0 or later
   • Upgrade electron to 40.7.0 or later
   • Upgrade electron to 41.0.0-beta.8 or later