CVE-2025-36929: Google Android · Information Disclosure
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Dec 2025
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 26 Oct 2026.
What to do
AI-suggested
Organizations should prioritize patch management by applying security updates from Google or device manufacturers as soon as patches for CVE-2025-36929 become available. Until patches are deployed, restricting installation of untrusted or unknown applications can reduce the risk of local exploitation. Employing mobile device management (MDM) solutions to enforce application whitelisting and limit local access can help mitigate exposure. Monitoring devices for unusual local activity or privilege escalation attempts can provide early detection of exploitation attempts. Educating users about the risks of installing unverified applications and maintaining strict physical device security policies will further reduce risk. For high-security environments, consider isolating critical Android devices or limiting their use to trusted applications only. Vendors and developers should review and improve input validation in kernel components to prevent similar vulnerabilities. Finally, organizations should maintain an inventory of Android devices and their kernel versions to identify and prioritize vulnerable endpoints.
Description
In AreFencesRegistered of gxp_fence_manager.cc, there is a possible information leak due to improper input validation. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.