CVE-2025-36911
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
- 7.1Highscored by CISA
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 8.4%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 15 Jan 2026analysed here 12 Nov 2026
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- adjacent network
- Can a WAF block it?
- No. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Google Android | Android kernelVendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- google:android
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack does not come over the network, so a WAF is not on its path. Patching is the reliable fix.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 11 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable no, technical impact partialAssessed by CISA 15 Jan 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- zalexdev/wpair-app865 stars
- KULeuven-COSIC/WhisperPair114 stars
- SpectrixDev/DIY_WhisperPair108 stars
- Ymsniper/Whisper_Bully40 stars
and 7 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 15 Jan 2026CISA SSVC assessment: exploitation none
- 15 Jan 2026Publishedsame day later
- 17 Jan 2026First proof-of-concept repository on GitHub (unvetted)1 day later
- 28 Jan 2026CVE record last updated11 days later
- 12 Nov 2026Analysed by vulneraibility.com288 days (about 10 months) later
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | AdjacentSame subnet or link layer. | Same subnet or link layer. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | LowLimited modification possible. | Limited modification possible. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2025-36911 being exploited?
Not confirmed. CVE-2025-36911 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 8.4% probability of exploitation in the next 30 days.
How severe is CVE-2025-36911?
CVE-2025-36911 is rated High with a CVSS score of 7.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-36911?
Yes. A fix has been recorded for CVE-2025-36911. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-36911 affect?
CVE-2025-36911 affects google:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Advisories (2)
- source.android.com /docs/security/bulletin/pixel/2026/2026-01-01
- whisperpair.eu /
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.