CVE-2025-36911VulnerabilityPublished 15 Jan 2026Updated 28 Jan 2026

CVE-2025-36911: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 8.4% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GoogleAndroid	Affected =Android kernel	Fixed in–

AI-suggested

1. Monitor official Google and Android vendor channels closely for the release of security patches addressing CVE-2025-36911 and prioritize their deployment across all affected devices in the organization. 2. Implement physical security controls to limit unauthorized individuals' proximity to employees' Android devices, especially in sensitive environments, to reduce the risk of adjacent network exploitation. 3. Educate employees about the risks of using wireless pairing features in public or unsecured locations and encourage disabling Bluetooth or similar wireless interfaces when not in use. 4. Employ mobile device management (MDM) solutions to enforce security policies that restrict or monitor wireless communications and pairing activities on corporate Android devices. 5. Use network segmentation and wireless intrusion detection systems (WIDS) to detect anomalous wireless activity that could indicate attempts to exploit this vulnerability. 6. For high-risk personnel, consider using devices with alternative operating systems or hardened configurations that are not affected by this vulnerability until patches are available. 7. Regularly audit and update device firmware and software to minimize exposure to kernel-level vulnerabilities. 8. Collaborate with cybersecurity teams to develop incident response plans specific to information disclosure incidents involving mobile devices.

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.

Impact

For European organizations, the impact of CVE-2025-36911 is primarily on the confidentiality of sensitive information. The vulnerability enables attackers in close physical proximity to intercept or extract private conversations and location data from Android devices without any user interaction or elevated privileges. This can lead to privacy violations, corporate espionage, and targeted surveillance, especially for organizations handling sensitive or classified information. Sectors such as government, defense, finance, and critical infrastructure are particularly at risk due to the potential exposure of confidential communications and location tracking of key personnel. The ease of exploitation combined with the widespread use of Android devices in Europe increases the likelihood of targeted attacks in urban and corporate environments where attackers can physically approach victims. Although the vulnerability does not affect system integrity or availability, the breach of confidentiality alone can have severe operational and reputational consequences. Additionally, the lack of known exploits in the wild currently provides a window of opportunity for organizations to implement mitigations before active exploitation occurs. However, failure to address the vulnerability promptly could result in increased risks from espionage and privacy breaches, especially in high-value targets.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 19:19 UTC

Technical details

References

Community reviews

Related threats