# CVE-2025-36911: Information disclosure in Android

> A logic error in Android key-based pairing allows remote attackers to disclose user conversations and location without user interaction.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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:** 15 Jan 2026
- **Updated:** 28 Jan 2026
- **Also known as:** A-445196906, GHSA-6fxf-xg6m-34hj, PUB-A-445196906

## What is CVE-2025-36911?

CVE-2025-36911 is a high-severity vulnerability in Google Android, published on 15 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-36911?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2025-36911?

Apply the vendor's patch.

## Is CVE-2025-36911 being exploited?

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

Public exploit code:

- 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. (github_poc): https://github.com/zalexdev/wpair-app
- The official reference implementation & vulnerability verification of our attack WhisperPair (CVE-2025-36911) which affects Google's Fast Pair protocol. (github_poc): https://github.com/KULeuven-COSIC/WhisperPair
- Hijacking Bluetooth Accessories Using Google Fast Pair: WhisperPair CVE-2025-36911 Reference Implementation & Vulnerability Verification Toolkit (github_poc): https://github.com/SpectrixDev/DIY_WhisperPair
- Three-stage Bluetooth BDADDR extraction, DoS & hijack on Fast Pair devices; unpatched primitives outside CVE-2025-36911 scope (no Ubertooth needed) (github_poc): https://github.com/Ymsniper/Whisper_Bully
- Exploit of the CVE-2025-36911 vulnerability in Python for testing our own equipment (github_poc): https://github.com/PentHertz/CVE-2025-36911-exploit
- WhisperPair (CVE-2025-36911) POC for ESP32 device  (github_poc): https://github.com/PivotChip/FrostedFastPair

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36911 and fix it if it is affected.

What it is: CVE-2025-36911 is a high-severity vulnerability in Google Android, published on 15 Jan 2026. 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-2025-36911 in the wild and no public exploit code.

Affected product: Google Android. 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-2025-36911/ (Markdown: https://insights.sbomify.com/CVE-2025-36911/index.md)
```

## Sources

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

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