NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
LOW severity

CVE-2022-21718 — electron

LOWFix: electron/electron#32178

CVE-2022-21718 is a low-severity (CVSS 3.4) CWE-668 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Renderers can obtain access to random bluetooth device without permission in Electron

Also known asGHSA-3p22-ghq8-v749
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk
0.35%0.71%1.08%1.45%0.8%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
electronnpm
12.5Mdownloads / week

Description

Impact

This vulnerability allows renderers to obtain access to a random bluetooth device via the web bluetooth API if the app has not configured a custom select-bluetooth-device event handler. The device that is accessed is random and the attacker would have no way of selecting a specific device.

All current stable versions of Electron are affected.

Patches

This has been patched and the following Electron versions contain the fix:

  • 17.0.0-alpha.6
  • 16.0.6
  • 15.3.5
  • 14.2.4
  • 13.6.6

Workarounds

Adding this code to your app can workaround the issue.

app.on('web-contents-created', (event, webContents) => {
  webContents.on('select-bluetooth-device', (event, devices, callback) => {
    // Prevent default behavior
    event.preventDefault();
    // Cancel the request
    callback('');
  });
});

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

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectronall versions13.6.6npm install electron@13.6.6
📦npmelectron≥ 14.0.0-beta.1&&< 14.2.414.2.4npm install electron@14.2.4
📦npmelectron≥ 15.0.0-beta.1&&< 15.3.515.3.5npm install electron@15.3.5
📦npmelectron≥ 16.0.0-beta.1&&< 16.0.616.0.6npm install electron@16.0.6
📦npmelectron≥ 17.0.0-alpha.1&&< 17.0.0-alpha.617.0.0-alpha.6npm install electron@17.0.0-alpha.6

Affected Products

1 product · 9 configurations
Application
electronelectronjs
≥ 16.0.0 && < 16.0.6
1 version
17.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update electron to 13.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21718 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact This vulnerability allows renderers to obtain access to a random bluetooth device via the [web bluetooth API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetooth_API) if the app has not configured a custom `select-bluetooth-device` event handler. The device that is accessed is random and the attacker would have no way of selecting a specific device. All current stable versions of Electron are affected. ### Patches This has been patched and the following Electron versions contain the fix: * `17.0.0-alpha.6` * `16.0.6` * `15.3.5` * `14.2.4` * `13.6.6` ### Workarounds Ad
O3 Security · Impact-Aware SCA

Is CVE-2022-21718 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-21718: electron — Fixed in 13.6.6