# CVE-2020-26558: Security feature bypass in n/a > A nearby attacker can bypass Bluetooth pairing authentication by reflecting keys to determine the Passkey bit-by-bit, allowing unauthorized device pairing. - **Severity:** Medium 4.2 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 May 2021 - **Updated:** 4 Nov 2025 - **Also known as:** A-174886838, ASB-A-174886838, DEBIAN-CVE-2020-26558, GHSA-7g33-jchx-2fjc, RHSA-2021:4432, UBUNTU-CVE-2020-26558 ## What is CVE-2020-26558? CVE-2020-26558 is a medium-severity vulnerability in Debian Debian Linux, published on 24 May 2021. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Bluetooth LE and BR/EDR secure pairing in Bluetooth Core Specification 2.1 through 5.2 may permit a nearby man-in-the-middle attacker to identify the Passkey used during pairing (in the Passkey authentication procedure) by reflection of the public key and the authentication evidence of the initiating device, potentially permitting this attacker to complete authenticated pairing with the responding device using the correct Passkey for the pairing session. The attack methodology determines the Passkey value one bit at a time. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2020-26558? It affects 19 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bluez-cups` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.56-1.el8 | | `bluez` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-hid2hci` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-obexd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.56-1.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-libs-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.56-1.el8 | Products: Bluetooth Bluetooth Core Specification, Debian Debian Linux, Fedoraproject Fedora, Intel Ac 1550 Firmware, Intel Ac 3165 Firmware, Intel Ac 3168 Firmware, Intel Ac 7265 Firmware, Intel Ac 8260 Firmware, Intel Ac 8265 Firmware, Intel Ac 9260 Firmware, Intel Ac 9461 Firmware, Intel Ac 9462 Firmware, Intel Ac 9560 Firmware, Intel Ax1650 Firmware, Intel Ax1675 Firmware, Intel Ax200 Firmware, Intel Ax201 Firmware, Intel Ax210 Firmware, Linux kernel. ## How do I fix CVE-2020-26558? Apply the vendor's patch. ## Is CVE-2020-26558 being exploited? There is no known exploitation of CVE-2020-26558 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2022-25836](https://insights.sbomify.com/CVE-2022-25836/): Auth bypass in n/a (high 7.5) - [CVE-2022-25837](https://insights.sbomify.com/CVE-2022-25837/): Auth bypass in n/a (high 7.5) - [CVE-2020-26556](https://insights.sbomify.com/CVE-2020-26556/): Auth bypass in n/a (high 7.5) - [CVE-2023-24023](https://insights.sbomify.com/CVE-2023-24023/): Weak cryptography in n/a (medium 6.4) - [CVE-2020-15802](https://insights.sbomify.com/CVE-2020-15802/): Auth bypass in n/a (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-26558 and fix it if it is affected. What it is: CVE-2020-26558 is a medium-severity vulnerability in Debian Debian Linux, published on 24 May 2021. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-26558 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-26558/ (Markdown: https://insights.sbomify.com/CVE-2020-26558/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26558 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26558 - OSV: https://osv.dev/vulnerability/CVE-2020-26558 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-26558/ Summaries are generated and may contain mistakes; the official description above is the record.