CVE-2025-36911

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

High · published January 15, 2026

CVSS v3.1
7.1
EPSS
8%
Percentile
95.0
In the wild
Unconfirmed
What it is

⚡ A sneaky logic error in key-based pairing poses a serious threat, allowing attackers to disclose sensitive conversations and location information without needing any special permissions! 🔍 This situation is like a delivery person misreading your package label and accidentally sharing your private notes with everyone nearby. The courier just trusted the label without checking who actually sent it! 📦 An attacker could potentially eavesdrop on your private conversations or track your location, leading to serious privacy breaches. Imagine someone having access to your most confidential discussions just because of a small oversight in the code. This is not just inconvenient; it could be downright alarming!

Put simply

This situation is like a delivery person misreading your package label and accidentally sharing your private notes with everyone nearby. The courier just trusted the label without checking who actually sent it! 📦 This vulnerability arises from a logic error in the key-based pairing process, enabling unauthorized access to sensitive user data without needing any additional execution privileges. User interaction is not necessary, making it even more concerning.

What to do

An attacker could potentially eavesdrop on your private conversations or track your location, leading to serious privacy breaches. Imagine someone having access to your most confidential discussions just because of a small oversight in the code. This is not just inconvenient; it could be downright alarming! To mitigate this risk, developers should review the key-based pairing logic and implement necessary patches as soon as possible. Ensure to audit the affected versions and update to the latest secure version once available. Always enforce robust security measures to safeguard user data! You’ve got this! By following these steps, you can help protect users from this vulnerability and earn your security hero badge! 🛡️

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CVSS v4.0
Not supplied
EPSS
0.08411 · 95.0th percentile
Published
2026-01-15T17:41Z
EPSS history
Timeline
  • 15 JAN 17:41Z
    In key-based pairing, there is a possible ID due to a logic error in the code
    cvelistv5