dbcve.org
ElectronApplication · Electronjs

CVE-2026-34766

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-04
Fix available
A fix is available. Upgrade to 38.8.6 / 39.8.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, 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. This issue has been patched in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Electron's WebUSB API contains a validation bypass in the select-usb-device event callback. Prior to versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, the handler did not validate that the chosen device ID matched the filtered list presented to the renderer, potentially allowing access to devices outside the requested filters or exclusionFilters. The WebUSB blocklist remained enforced.

MitigationUpgrade Electron to version 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 or later. Applications using unusual device-selection logic should verify their handlers properly validate device IDs against the filtered set.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectronApplication
Affected:< 38.8.6>= 39.0.0, < 39.8.0>= 40.0.0, < 40.7.0= 41.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Electron version
    Run 'electron --version' from command line, check package.json dependencies, or inspect process.versions.electron in the running application
    Affected if The version falls outside 38.8.6+, 39.8.0+, 40.7.0+, or 41.0.0-beta.8+ (i.e., it is below these or exactly 41.0.0)
  2. Verify WebUSB API usage
    Search codebase for 'navigator.usb' or '@electron/remote' USB module usage in renderer process JavaScript
    Affected if WebUSB API is used in the application renderer
  3. Identify select-usb-device event handlers
    Search for '.on("select-usb-device",' or 'select-usb-device' event listener registrations in the main process code
    Affected if A select-usb-device event handler is registered
  4. Examine handler device selection logic
    Review the select-usb-device handler code to determine if it uses deviceId from the event without validating against the filters array provided in the event
    Affected if The handler uses event.deviceId without cross-checking event.filters or event.exclusionFilters

You are affected if your Electron version is below the fixed releases AND your application uses WebUSB with a select-usb-device event handler that does not validate selected device IDs against the provided filter list.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 38.8.6 / 39.8.0 / 40.7.0 or later
Fixed in 38.8.639.8.040.7.0
Interim mitigation

Upgrade Electron to version 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 or later. Applications using unusual device-selection logic should verify their handlers properly validate device IDs against the filtered set.

Recommended fix High confidence

Electron 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 (depending on your current major version)

  1. 1. Identify your current Electron version by checking package.json or running `npm list electron`
  2. 2. Determine which major version you are currently on (38.x, 39.x, 40.x, or 41.x)
  3. 3. If on version < 38.8.6, upgrade to version 38.8.6
  4. 4. If on version >= 39.0.0 and < 39.8.0, upgrade to version 39.8.0
  5. 5. If on version >= 40.0.0 and < 40.7.0, upgrade to version 40.7.0
  6. 6. If on version 41.0.0, upgrade to version 41.0.0-beta.8
  7. 7. Update your package.json with the new version and run `npm install` or `npm update electron`
  8. 8. Test your application, particularly any WebUSB functionality that uses the select-usb-device event
Caveat Minor - the fix adds validation to select-usb-device callback; apps with normal device-selection logic should not be affected, but test WebUSB functionality thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Electron Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34766 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data