Red Hat CVE-2026-34766
MEDIUMVulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents low real-world risk despite affecting a widely-used framework. The CVSS 3.3 score reflects the limited attack surface: local attack vector (AV:L), high complexity (AC:H), authenticated user requirement (PR:L), and mandatory user interaction (UI:R) create substantial friction for exploitation. The symmetric impact (C:L, I:L, A:N) indicates the attacker gains limited confidentiality and integrity access without availability impact. The authentication requirement (PR:L) and UI interaction constraint mean exploitation requires either a compromised local user account or social engineering to manipulate the UI element. The description explicitly states the practical impact is limited to applications with unusual device-selection logic, suggesting this is not a general-purpose bypass affecting typical WebUSB usage. The fact that the security blocklist remains enforced is a critical mitigating control-devices most sensitive to unauthorized access (FIDO keys, security tokens) cannot be accessed via this bypass. No EPSS score, KEV status, or POC availability data was provided, but the constraint profile (local + authenticated + UI interaction + limited scope) suggests this is unlikely to be actively exploited in the wild; however, it remains a valid bypass in targeted scenarios where an attacker has local access and can influence application UI behavior. |
| Exploit ScenarioDerived | An attacker with local access to a system running a vulnerable Electron application could craft a scenario where the application's device selection UI is presented to a user (e.g., a browser requesting USB access for a peripheral). By manipulating the selection mechanism or exploiting application-specific device selection logic, the attacker influences the handler to select a device ID that was not in the originally filtered list, thereby gaining access to a USB device that should have been restricted by the application's exclusion filters. This requires the attacker to either compromise a local user account or perform UI-level social engineering, making it a targeted attack rather than a mass exploitation vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 03, 2026
Electron's WebUSB device selection handler fails to validate chosen device IDs against renderer-requested filters, allowing authenticated local users with UI interaction to bypass intended device access restrictions and gain access to unfiltered USB devices. The vulnerability affects Electron versions prior to 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, with CVSS 3.3 (low severity) due to local-only attack vector and UI interaction requirement; the WebUSB security blocklist remains enforced, limiting practical impact to applications with non-standard device selection logic.
RemediationAI
Vendor-released patches are available for all supported versions: upgrade to Electron 38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8 depending on your current major version. No application-side workarounds exist; patching is mandatory. Review your application's WebUSB implementation and device selection logic after patching to ensure filters are correctly specified. Consult the official GitHub Security Advisory at https://github.com/electron/electron/security/advisories/GHSA-9899-m83m-qhpj for version-specific upgrade guidance and contact security@electronjs.org with any questions.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Electron's WebUSB API implementation includes a device selection mechanism that presents users with a filtered list of USB devices based on the renderer process's requested filters and exclusion filters. The vulnerability exists in the select-usb-device event callback handler, which failed to validate that the device ID ultimately selected by the user matched the original filtered device set presented to them. This represents a missing authorization check (CWE-862: Missing Authorization) where the main process accepted a device selection without re-verifying it against the declared filter constraints. While the WebUSB security blocklist-a hardcoded list of security-sensitive devices like FIDO keys-remained enforced at a lower layer, the filter bypass allows access to devices outside the originally requested scope. The npm package 'electron' across multiple major versions contained this validation gap in its USB device enumeration and selection logic.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Impact
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.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
41.0.0-beta.840.7.039.8.038.8.6
For more information
If there are any questions or comments about this advisory, send an email to [security@electronjs.org](mailto:security@electronjs.org)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
GHSA-9899-m83m-qhpj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB