Skip to main content
Public proof of conceptFix available

CVE-2025-36911

A public proof of concept exists; no exploitation attested.

  • Published2026-01-15

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-01-1518:16CVE publishedNVD

Versions per branch

NVD
Google android
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Google_Devices, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Androidother versions: not affected
    Affected
    • = Android kernelno fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-01-28

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • :unknown:Androidfrom Pixel-family specific:0 · fixed in Pixel-family specific:2026-01-05

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Published
2026-01-15
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-6fxf-xg6m-34hj

Frequently asked questions

What is 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.

Is CVE-2025-36911 actively exploited?

Active exploitation of CVE-2025-36911 has not been confirmed. Its EPSS score was 8.4% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-36911?

CVE-2025-36911 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.

Running :unknown:? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record