Skip to content
Fencer Vulns
high 7.1

CVE-2025-36911 json

In key-based pairing, there is a possible ID due to a logic error in the code.

published 2026-01-15 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-2722

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
8.4%
EPSS 8.4% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

8.41% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • whisperpair.eu https://whisperpair.eu/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.1 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA 3.1 7.1 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected products

  • Google Android

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.