CVE-2022-25836 is a pairing method confusion flaw (CWE-294) in Bluetooth LE Passkey Entry, Core Specification 4.0 to 5.3: a nearby attacker runs Legacy Passkey pairing with one device and Secure Connections Passkey pairing with the other, brute-forces the passkey and pairs as a man in the middle. NVD scores it 7.5. The Bluetooth SIG recommends Secure Connections Only mode.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2022-25836 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Bluetooth Core Specification LE Passkey Entry pairing | cpe:2.3:a:bluetooth:bluetooth_core_specification:*:*:*:*:*:*:*:* | 4.0 through 5.3 (NVD, Bluetooth SIG); mitigation: Secure Connections Only mode |
| Android (AOSP Bluetooth, System component) | — | addressed in Android 17, security patch level 2026-07-01 (Android 17 Security Release Notes, A-236134583); not in NVD's CPE configuration |
What does this mean for affected devices?
NVD's description: LE pairing "may permit an unauthenticated MITM to acquire credentials with two pairing devices via adjacent access when the MITM negotiates Legacy Passkey Pairing with the pairing Initiator and Secure Connections Passkey Pairing with the pairing Responder and brute forces the Passkey entered by the user into the Initiator." NVD's Primary score is 7.5, CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N, with CWE-294; CISA's ADP entry gives the same score and CWE. The CPE covers the Core Specification 4.0 through 5.3 (NVD).
How does the attack work?
The Bluetooth SIG notice, dated 2022-12-09 on the SIG's security notices page, credits researchers at ANSSI, the French national cybersecurity agency. The attacker sits between two devices pairing for the first time. It runs LE Legacy Passkey pairing with the initiator, which must support entry or display of a passkey, and LE Secure Connections Passkey pairing with the responder. The user has to enter the passkey shown by one device into its peer, or the same passkey into both. The attacker then finds the passkey entered into the initiator "by a real-time brute force search" and uses it to complete authenticated pairing with the responder, "even if operating in Secure Connections Only Mode". The attacker must be in radio range during first-time pairing.
Who has shipped a fix?
The flaw is in the specification, so fixes come from stack vendors. Google lists CVE-2022-25836 (A-236134583, elevation of privilege, High) in the System component of the Android 17 Security Release Notes, published on 2026-06-16; devices on Android 17 with security patch level 2026-07-01 or later are protected. Ubuntu marks the bluez package "Ignored" with no fix to be provided and the Linux kernel "Vulnerable, fix deferred" in its supported releases as of 2026-11-18. NVD lists no product CPEs beyond the specification.
What should device makers do?
The SIG recommends that "implementations enforce Secure Connections Only Mode": if both devices refuse LE Legacy pairing, the attacker cannot force it on either. Where Legacy pairing must stay, the SIG asks products to show clearly which pairing mode is in use so users do not reuse one passkey for the other. Check that your firmware's stack has a Secure Connections Only setting and that it is on. Our Bluetooth LE security guide covers pairing modes, and the authentication bypass fix guide covers the weakness class. Related: CVE-2020-26558 (Passkey Entry impersonation), CVE-2020-15802 (BLURtooth) and CVE-2023-24023 (BLUFFS).
CVE-2022-25836 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0038, the 33.0th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- LE pairing in Core 4.0 through 5.3 may permit an unauthenticated MITM via Legacy Passkey with Initiator and Secure Connections Passkey with Responder, brute forcing the passkey; NVD Primary 7.5 AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N; CWE-294 (NVD and CISA-ADP); CISA-ADP 7.5 same vector; CPE core spec 4.0 through 5.3; published 2022-12-12. — NVD
- Researchers at ANSSI; MITM negotiates LE Legacy Passkey with Initiator and LE Secure Connections Passkey with Responder; user must enter displayed passkey into peer or the same passkey into both; real-time brute force; even if operating in Secure Connections Only Mode; recommends enforcing Secure Connections Only Mode and clearly indicating pairing mode in UI. — Bluetooth SIG
- SIG security notices table: Pairing Mode Confusion in Bluetooth LE Passkey Entry, 09/12/2022, Core Spec v4.0 to 5.3, CVE-2022-25836. — Bluetooth SIG
- Android 17 Security Release Notes, published June 16, 2026, updated September 3, 2026; System: CVE-2022-25836 A-236134583 EoP High; Android 17 devices with security patch level 2026-07-01 or later protected. — Android Open Source Project
- bluez: Ignored, no fix will be provided; linux: Vulnerable, fix deferred in supported releases (checked 2026-11-18). — Ubuntu security
- Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.00384, percentile 0.32991, dataset 2026-11-17, read 2026-11-18. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does Secure Connections Only mode stop CVE-2022-25836?
Yes, when both devices use it. The SIG says that if both devices are in Secure Connections Only Mode, the attacker cannot force LE Legacy Pairing with either; the attack works when one side still accepts Legacy Passkey pairing (per the Bluetooth SIG).
Which Android version fixes CVE-2022-25836?
Google lists it in the Android 17 Security Release Notes (A-236134583, High); Android 17 devices with security patch level 2026-07-01 or later are protected (per the Android 17 Security Release Notes).
What does the attacker need for CVE-2022-25836?
Radio range during first-time pairing, one device that supports LE Legacy Passkey entry, and a user who enters the displayed passkey into the peer or the same passkey into both devices (per the Bluetooth SIG and NVD).
Is CVE-2022-25836 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0038, the 33.0th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?