# CVE-2020-26555: Auth bypass in n/a

> An attacker can bypass Bluetooth PIN authentication by spoofing the peer device address, allowing unauthorized pairing.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:L/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-174626251, ASB-A-174626251, GHSA-6vq6-ghrc-jpjw, UBUNTU-CVE-2020-26555

## What is CVE-2020-26555?

CVE-2020-26555 is a medium-severity authentication bypass vulnerability in Fedoraproject Fedora, 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 legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2020-26555?

It affects 17 products.


Products: Bluetooth Bluetooth Core Specification, Fedoraproject Fedora, 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 Ax200 Firmware, Intel Ax201 Firmware, Intel Ax210 Firmware, Intel Killer Ac 1550 Firmware, Intel Killer Wi-Fi 6 Ax1650 Firmware, Intel Killer Wi-Fi 6e Ax1675 Firmware.

## How do I fix CVE-2020-26555?

Apply the vendor's patch.

## Is CVE-2020-26555 being exploited?

There is no known exploitation of CVE-2020-26555 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [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-26555 and fix it if it is affected.

What it is: CVE-2020-26555 is a medium-severity authentication bypass vulnerability in Fedoraproject Fedora, 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-26555 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-26555/ (Markdown: https://insights.sbomify.com/CVE-2020-26555/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26555
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26555
- OSV: https://osv.dev/vulnerability/CVE-2020-26555

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26555/
Summaries are generated and may contain mistakes; the official description above is the record.