CVE-2021-1638

Peer impersonation via Passkey bit recovery

Published Jan 12, 2021 · Updated Oct 8, 2024

Bluetooth authentication bypass in affected Microsoft Windows releases allows physically proximate attackers to impersonate a pairing peer. The Passkey Entry exchange accepts crafted round-by-round responses that reveal each random passkey bit, then accepts those bits within the same pairing session. The attacker must be within wireless range of two vulnerable devices starting Passkey pairing; exploitation authenticates the responder to the attacker as an encrypted peer, not to the intended initiator.

CVSS severity7.7
High
EPSS probability1.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Bluetooth authentication bypass in affected Microsoft Windows releases allows physically proximate attackers to impersonate a pairing peer. The Passkey Entry exchange accepts crafted round-by-round responses that reveal each random passkey bit, then accepts those bits within the same pairing session. The attacker must be within wireless range of two vulnerable devices starting Passkey pairing; exploitation authenticates the responder to the attacker as an encrypted peer, not to the intended initiator.

The record

CVE
CVE-2021-1638
Published
Jan 12, 2021
Updated
Oct 8, 2024
Vendor
Microsoft
Product
Windows Server 2019
Classifications
T1557
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 12, 2021CVE publishedPublication date reported by the CVE source.
  2. Oct 8, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.0 <publication

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.0 <publication
Microsoft · Windows 10 Version 1909version=10.0.0 <publication
Microsoft · Windows 10 Version 1803version=10.0.0 <publication
Microsoft · Windows Server, version 2004version=10.0.0 <publication
Microsoft · Windows 10 Version 20H2version=10.0.0 <publication
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.0 <publication
Microsoft · Windows Server version 20H2version=10.0.0 <publication
Microsoft · Windows 10 Version 2004version=10.0.0 <publication
Microsoft · Windows 10 Version 1809version=10.0.0 <publication
Microsoft · Windows Server, version 1909 (Server Core installation)version=10.0.0 <publication

Published CVSS scores

2.1NISTAV:L/AC:L/Au:N/C:P/I:N/A:N
5.5NISTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
7.7Microsoft CorporationCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo