Skip to main content
CVE-2025-36891VulnerabilityPublished Updated

CVE-2025-36891: Google Android · Elevation of privilege

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

AI-suggested

Organizations should implement the following specific mitigations: 1) Monitor official Google security advisories and Android security bulletins closely for the release of patches addressing CVE-2025-36891 and apply them promptly to all affected devices. 2) Employ mobile device management (MDM) solutions to enforce strict privilege separation and limit the installation of untrusted applications that could leverage this vulnerability. 3) Restrict network access to Android devices, especially from untrusted or public networks, to reduce exposure to remote exploitation. 4) Use security features such as SELinux enforcing mode and verified boot to limit the impact of privilege escalation attempts. 5) Conduct regular audits of device privilege configurations and remove unnecessary elevated privileges from applications and users. 6) Educate users and administrators about the risks of privilege escalation vulnerabilities and encourage prompt installation of security updates. 7) For organizations deploying Android in embedded or IoT contexts, consider additional hardening and monitoring to detect anomalous kernel-level activity. These steps go beyond generic advice by focusing on privilege management, network exposure reduction, and proactive patch management tailored to the Android kernel environment.

Description

Elevation of privilege

References

Community reviews

Loading reviews…