In key-based pairing, there is a possible ID due to a logic error in the code. This could lead to remote (proximal/adjacent) information disclosure of user's conversations and location with no additional execution privileges needed. User interaction is not needed for exploitation.
Severity
CVSS 3.1
7.1 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
8.4%(unchanged from 8.4% a week ago; 8.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 95th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-01-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2025-36911 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-36911?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-36911?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-36911 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
zalexdev/wpair-appHarbor Check: matches CVE865 stars, created WPair is a defensive security research tool that demonstrates the CVE-2025-36911 (eg WhisperPair) vulnerability in Google's Fast Pair proto…
SpectrixDev/DIY_WhisperPairHarbor Check: matches CVE109 stars, created Hijacking Bluetooth Accessories Using Google Fast Pair: WhisperPair CVE-2025-36911 Reference Implementation & Vulnerability Verification To…
PentHertz/CVE-2025-36911-exploitHarbor Check: matches CVE27 stars, Python, created Exploit of the CVE-2025-36911 vulnerability in Python for testing our own equipment
PivotChip/FrostedFastPairHarbor Check: matches CVE15 stars, created WhisperPair (CVE-2025-36911) POC for ESP32 device
ap425q/whisper-pairHarbor Check: matches CVE2 stars, created A Vulnerablity Scanner for Whisper Pair (CVE-2025-36911)
4 more
markmysler/wpair-cliHarbor Check: matches CVE2 stars, created Defensive scanner for CVE-2025-36911, the Google Fast Pair Bluetooth vulnerability.
jvitor211/TheyListenHarbor Check: matches CVE0 stars, created Security research tool demonstrating CVE-2025-36911 (WhisperPair) in Google Fast Pair devices.
Cedric-Martz/CVE-2025-36911_scan3 stars, Python, created This script can be used to check if a Bluetooth device is vulnerable to CVE-2025-36911.
SteamPunk424/CVE-2025-36911-Wisper_Pair_Target_Finder2 stars, Python, created This is not an exploit for CVE-2025-36911!!! This is a detector for finding potentially vulnerable devices! Only use on your own devices! I…