CVE-2020-10135, the BIAS attack, is a flaw in Bluetooth BR/EDR authentication in Core Specification v5.2 and earlier: an attacker in radio range impersonates a device the victim has already bonded with and completes authentication without the link key, by downgrading to legacy authentication and switching roles. NVD scores it 5.4. Fixes come as host stack and controller firmware updates.
Vulnerability summary
CVSS base score
5.4
Medium severity
EPSS score (FIRST)
2.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-10135 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Bluetooth Core Specification BR/EDR (legacy and Secure Connections authentication) | cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:br:*:*:* | v5.2 and earlier (NVD, CVE record); Core v2.1 to v5.2 (Bluetooth SIG security notice list) |
| Linux kernel Bluetooth stack | — | fixed upstream in 5.9-rc1, 5.4.72 and 4.4.240; Ubuntu focal 5.4.0-56.62, bionic 4.15.0-129.132, xenial 4.4.0-197.229 (Ubuntu CVE tracker) |
| Jabra headsets and speakerphones (e.g. Link 370, Evolve 75, Speak 710, Engage 65/75, Elite 65t) | — | fixed in Link 370 1.48.0, Evolve 75 2.10.0, Speak 710 1.38.0, Engage 65/75 4.2.0, Elite 65t 2.34.0 and others listed; products launched after 31 October 2019 not affected (Jabra Security Incident Bulletin 250923) |
What does this mean for affected devices?
CVE-2020-10135, known as BIAS (Bluetooth Impersonation AttackS), is a flaw in the authentication procedure of Bluetooth BR/EDR (Classic) in the Bluetooth Core Specification v5.2 and earlier. An attacker in radio range spoofs the address of a device the victim has already bonded with and completes authentication without knowing the link key. NVD's Primary score is 5.4, CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, with CWE-290 (authentication bypass by spoofing). CERT/CC, the CNA, gives the same 5.4 vector and classes it as CWE-757 (algorithm downgrade). The record was published on 2020-05-19 (NVD, CVE record).
How does the BIAS attack work?
CERT/CC VU#647177 describes two paths. If the devices bonded with Secure Connections, the attacker claims the remembered peer no longer supports Secure Connections and drops to legacy authentication, unless the victim runs in Secure Connections Only mode. In legacy authentication the attacker then performs a role switch to become the authentication initiator; if the victim does not authenticate the attacker in return, both sides report authentication complete although the attacker has no link key. The Bluetooth SIG statement adds that the attacker may then negotiate a short encryption key on devices still open to the 2019 KNOB attack, CVE-2019-9506, and brute-force it; without that, the attacker gets no encrypted link but may still appear authenticated to the host. The researchers at EPFL, CISPA and Oxford report that all 30 devices they tested, with 28 chips from Cypress, Qualcomm, Apple, Intel, Samsung and CSR, were vulnerable. The attack needs a previously bonded pair and a Bluetooth address the attacker knows.
Which devices and firmware are affected?
Any BR/EDR product built on Core v5.2 or earlier; the SIG notice list gives Core v2.1 to v5.2. The fix lives in the host stack and, for some vendors, in controller firmware. Intel told CERT/CC its Bluetooth controllers are not affected, and CERT/CC notes the SIG concluded mutual authentication was always the host's responsibility. Device examples from advisories:
- Jabra's security bulletin lists firmware that fixes BIAS and KNOB, for example Link 370 1.48.0, Evolve 75 2.10.0, Speak 710 1.38.0, Engage 65/75 4.2.0 and Elite 65t 2.34.0, and says products launched after 31 October 2019 should not be affected.
- In the Linux kernel, the fixes "Bluetooth: Consolidate encryption handling in hci_encrypt_cfm" and "Bluetooth: Disconnect if E0 is used for Level 4" landed in 5.9-rc1, 5.4.72 and 4.4.240; Ubuntu fixed focal in 5.4.0-56.62 and bionic in 4.15.0-129.132 (Ubuntu CVE page). Embedded Linux gateways need a kernel at or past those versions.
How do you fix or mitigate CVE-2020-10135?
Install controller firmware and host stack updates from the chip and device vendor. The SIG announced Core Specification changes that clarify when role switches are permitted and require authenticating the peer in legacy authentication. Until a product has the update, the SIG asks vendors not to permit encryption keys shorter than 7 octets, to have the host start mutual authentication in legacy authentication, to support Secure Connections Only mode where possible, and not to treat Bluetooth authentication alone as a change of trust without an encrypted link. Red Hat suggests Secure Connections Only mode where legacy pairing is not needed, or disabling Bluetooth. Our NIST SP 800-121 guide covers the BR/EDR checklist and the authentication bypass fix guide covers the class. Related pairing flaws: BLURtooth, CVE-2020-15802, CVE-2020-26558, BLUFFS, CVE-2023-24023 and CVE-2022-25836.
Is CVE-2020-10135 exploited?
The researchers published instructions and code for the attack (BIAS repository). CVE-2020-10135 is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.02386, the 84.3rd percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may allow an unauthenticated adjacent user to complete authentication without pairing credentials; NVD Primary CVSS v3.1 5.4 AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-290; CERT/CC secondary 5.4 same vector, CWE-757; CPE bluetooth_core br/edr up to 5.2; published 2020-05-19. Read 2026-11-19. — NVD
- CVE.org: state PUBLISHED, CNA CERT/CC (certcc), published 2020-05-19; CNA CVSS 3.1 5.4; affected Bluetooth BR/EDR up to and including 5.2. Read 2026-11-19. — CVE.org
- Bluetooth SIG statement: attacker spoofing a previously bonded device can complete authentication without the link key; Secure Connections downgrade unless Secure Connections Only mode; role switch to become initiator; may combine with KNOB; SIG updating the Core Specification; interim recommendations: no key length below 7 octets, host-initiated mutual authentication in legacy authentication, Secure Connections Only mode where possible, no trust change from authentication alone without an encrypted link. Read 2026-11-19. — Bluetooth SIG
- Bluetooth SIG reporting security vulnerabilities page: Bluetooth Impersonation Attacks notice of 18/05/2020, Core Spec v2.1 to v5.2, CVE-2020-10135. Read 2026-11-19. — Bluetooth SIG
- CERT/CC VU#647177 (first published 2020-05-18): two attack paths (Secure Connections downgrade, legacy authentication with role switch); can be combined with KNOB; solution: host and controller suppliers follow the SIG statement, downstream vendors get updates from suppliers; Intel states its Bluetooth controllers are not affected and CERT/CC notes the SIG concluded mutual authentication is the host's responsibility. Read 2026-11-19. — CERT/CC
- BIAS researchers (Antonioli, Tippenhauer, Rasmussen): disclosed to the SIG in December 2019; tested 30 devices with 28 unique chips from Cypress, Qualcomm, Apple, Intel, Samsung and CSR, all vulnerable. Read 2026-11-19. — BIAS research page
- francozappa/bias GitHub repository (created 2020-05-18): instructions to perform the BIAS attacks and code to validate the legacy and secure authentication procedures. Read 2026-11-19. — BIAS repository
- Jabra Security Incident Bulletin 250923: lists firmware fixing BIAS (CVE-2020-10135, 5.4) and KNOB, e.g. Link 370 1.48.0, Evolve 75 2.10.0, Speak 710 1.38.0, Engage 65/75 4.2.0, Elite 65t 2.34.0; products launched after 31 October 2019 should not be impacted. Read 2026-11-19. — Jabra (GN Audio)
- Linux commits 3ca44c16 'Bluetooth: Consolidate encryption handling in hci_encrypt_cfm' and 8746f135 'Bluetooth: Disconnect if E0 is used for Level 4' (Luiz Augusto von Dentz, 2020). Read 2026-11-19. — Linux kernel (GitHub mirror)
- Ubuntu CVE tracker: upstream linux fixed in 5.9~rc1, 4.4.240, 5.4.72 (break-fix 3ca44c16, 8746f135); Ubuntu linux fixed in focal 5.4.0-56.62, bionic 4.15.0-129.132, xenial 4.4.0-197.229. Read 2026-11-19. — Ubuntu
- Red Hat: mitigation is to enforce Secure Connections Only mode where legacy pairing is not needed, or disable Bluetooth; CWE-290. Read 2026-11-19. — Red Hat

Related advisories
Sources
- NVD
- CVE.org record CVE-2020-10135 (CNA: CERT/CC)
- Bluetooth SIG statement on BIAS
- Bluetooth SIG: reporting security vulnerabilities (security notice list)
- CERT/CC VU#647177
- BIAS: Bluetooth Impersonation AttackS (researchers' page)
- BIAS repository on GitHub (attack instructions and code)
- Jabra Security Incident Bulletin 250923: KNOB and BIAS
- Linux commit 8746f135: Bluetooth: Disconnect if E0 is used for Level 4
- Linux commit 3ca44c16: Bluetooth: Consolidate encryption handling in hci_encrypt_cfm
- Ubuntu CVE page: CVE-2020-10135
- Red Hat CVE page: CVE-2020-10135
- CISA KEV
- FIRST EPSS
Frequently asked questions
Is there a fixed version for CVE-2020-10135?
BIAS is a specification flaw, so the fix comes from each host stack and controller vendor. The Linux kernel fixed it in 5.9-rc1, 5.4.72 and 4.4.240, and Jabra lists fixed firmware such as Link 370 1.48.0 and Speak 710 1.38.0 (per the Ubuntu CVE tracker and Jabra Security Incident Bulletin 250923).
How can a device maker mitigate BIAS before an update ships?
Do not permit encryption keys shorter than 7 octets, have the host start mutual authentication in legacy authentication, support Secure Connections Only mode where possible, and do not treat Bluetooth authentication alone as a trust change without an encrypted link. Red Hat adds that disabling Bluetooth is an option where it is not needed (per the Bluetooth SIG statement and Red Hat).
Why do NVD and CERT/CC list different CWEs for CVE-2020-10135?
Both score it 5.4 with the same vector, AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. NVD classes it as CWE-290, authentication bypass by spoofing, while CERT/CC as the CNA classes it as CWE-757, algorithm downgrade, reflecting the Secure Connections downgrade step (per NVD and CVE.org).
Does BIAS affect Bluetooth Low Energy devices?
NVD and the CVE record describe a flaw in BR/EDR (Classic) authentication, and CERT/CC and the Bluetooth SIG describe the attack against BR/EDR bonding with legacy authentication and role switching. Pairing flaws that reach Low Energy are tracked under other CVEs, such as BLURtooth, CVE-2020-15802 (per NVD, CERT/CC VU#647177 and the Bluetooth SIG statement).
Is CVE-2020-10135 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). The researchers published instructions and code for the attack, and FIRST EPSS gives it 0.02386, the 84.3rd percentile, in the 2026-11-18 dataset (per CISA KEV, the researchers' BIAS repository and FIRST EPSS).
Questions about this page?