CVE-2025-36911

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-01-15. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 7%CVSS: 7.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
7%
EPSS %ILE
93%
KEV
Not listed

Published

January 15, 2026

Last Modified

June 17, 2026

References (2)

Data Freshness Timeline

(refreshed 6× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-01 04:15 UTCEPSS rescore
  2. 2026-07-30 16:27 UTCEPSS rescore
  3. 2026-07-30 01:29 UTCEPSS rescore
  4. 2026-07-28 15:35 UTCEPSS rescore
  5. 2026-07-25 14:17 UTCEPSS rescore
  6. 2026-07-25 14:17 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 02:54 UTCEG score recompute
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-21 15:24 UTCEPSS rescore
  12. 2026-07-20 17:07 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 01:59 UTCEPSS rescore
  23. 2026-07-15 01:59 UTCEPSS rescore
  24. 2026-07-13 22:29 UTCEPSS rescore
  25. 2026-07-13 22:29 UTCEPSS rescore
Show 60 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-09 19:09 UTCEPSS rescore
  5. 2026-07-09 19:09 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 04:55 UTCEPSS rescore
  21. 2026-06-28 04:55 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-24 14:04 UTCEPSS rescore
  27. 2026-06-24 14:04 UTCEPSS rescore
  28. 2026-06-23 21:32 UTCEPSS rescore
  29. 2026-06-23 21:32 UTCEPSS rescore
  30. 2026-06-19 19:25 UTCEPSS rescore
  31. 2026-06-19 19:25 UTCEPSS rescore
  32. 2026-06-18 17:52 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-17 17:52 UTCEPSS rescore
  35. 2026-06-16 17:52 UTCEPSS rescore
  36. 2026-06-16 17:52 UTCEPSS rescore
  37. 2026-06-14 23:17 UTCEPSS rescore
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-12 23:11 UTCEPSS rescore
  40. 2026-06-11 14:00 UTCEPSS rescore
  41. 2026-06-10 22:18 UTCEPSS rescore
  42. 2026-06-10 13:22 UTCEPSS rescore
  43. 2026-06-08 14:16 UTCEPSS rescore
  44. 2026-06-08 14:16 UTCEPSS rescore
  45. 2026-06-07 15:24 UTCEPSS rescore
  46. 2026-06-06 13:47 UTCEPSS rescore
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-05 22:46 UTCEPSS rescore
  49. 2026-06-05 22:46 UTCEPSS rescore
  50. 2026-06-04 13:12 UTCEPSS rescore
  51. 2026-06-04 13:12 UTCEPSS rescore
  52. 2026-06-02 20:12 UTCEPSS rescore
  53. 2026-06-01 13:51 UTCEPSS rescore
  54. 2026-06-01 13:51 UTCEPSS rescore
  55. 2026-05-31 22:30 UTCEPSS rescore
  56. 2026-05-31 22:30 UTCEPSS rescore
  57. 2026-05-31 00:16 UTCEPSS rescore
  58. 2026-05-29 15:51 UTCEG score recompute
  59. 2026-05-29 15:51 UTCGHSA enrichment
  60. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(9 references)

Working exploit code is in the public domain (9 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCYmsniper/Whisper_Bully
    First seen Jul 7, 2026

    Three-stage Bluetooth DoS attack & Hijack on Fast Pair devices via CVE-2025-36911 (no Ubertooth needed)

    Open source ↗
  • GitHub PoCKULeuven-COSIC/WhisperPair
    First seen Mar 30, 2026

    The official reference implementation & vulnerability verification of our attack WhisperPair (CVE-2025-36911) which affects Google's Fast Pair protocol.

    Open source ↗
  • GitHub PoCAthexblackhat/BLUE-SPY
    First seen Feb 19, 2026

    BLUE-SPY (Bluetooth Low Energy Universal Exploit - Security Penetration Testing) is a professional security assessment tool for analyzing CVE-2025-36911 vulnerabilities in Google's Fast Pair protocol implementation.

    Open source ↗
  • GitHub PoCPentHertz/CVE-2025-36911-exploit
    First seen Jan 27, 2026

    Exploit of the CVE-2025-36911 vulnerability in Python for testing our own equipment

    Open source ↗
  • GitHub PoCaalex954/whisperpair-poc-tool
    First seen Jan 25, 2026

    A security research tool that identifies and demonstrates the CVE-2025-36911: Fast Pair Pairing Mode Bypass vulnerability

    Open source ↗
  • GitHub PoCPivotChip/FrostedFastPair
    First seen Jan 20, 2026

    WhisperPair (CVE-2025-36911) POC for ESP32 device

    Open source ↗
  • GitHub PoCCedric-Martz/CVE-2025-36911_scan
    First seen Jan 17, 2026

    This script can be used to check if a Bluetooth device is vulnerable to CVE-2025-36911.

    Open source ↗
  • GitHub PoCzalexdev/wpair-app
    First seen Jan 17, 2026

    WPair is a defensive security research tool that demonstrates the CVE-2025-36911 (eg WhisperPair) vulnerability in Google's Fast Pair protocol. This vulnerability affects millions of Bluetooth audio devices worldwide, allowing unauthorized pairing and potential microphone access without user consent.

    Open source ↗
  • GitHub PoCSpectrixDev/DIY_WhisperPair
    First seen Jan 17, 2026

    Hijacking Bluetooth Accessories Using Google Fast Pair: WhisperPair CVE-2025-36911 Reference Implementation & Vulnerability Verification Toolkit

    Open source ↗

Frequently asked(5)

What is CVE-2025-36911?
CVE-2025-36911 is a high vulnerability published on January 15, 2026. 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.
When was CVE-2025-36911 disclosed?
CVE-2025-36911 was first published in the National Vulnerability Database on January 15, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36911 actively exploited?
CVE-2025-36911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7% probability of exploitation in the next 30 days, which ranks it in the top 6.6% of all scored CVEs.
What is the CVSS score of CVE-2025-36911?
CVE-2025-36911 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-36911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36911, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-36911

Explore →

Is Your Infrastructure Affected by CVE-2025-36911?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs