Skip to main content
VulnerabilityPublished

CVE-2025-26429: Google Android · Denial of Service

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% 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:N/I:N/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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =15
  • =14
  • =13
Fixed in–

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Monitor for official patches or updates from Google and Android device manufacturers and deploy them promptly once available. 2) Implement strict device access controls to limit local access to authorized personnel only, including enforcing strong lock screen protections and device encryption. 3) Employ mobile device management (MDM) solutions to monitor device health and detect abnormal behavior indicative of attempted exploitation. 4) Educate users about the risks of granting device access to untrusted parties and the importance of physical device security. 5) For high-risk environments, consider restricting use of affected Android versions or deploying alternative devices until patches are available. 6) Maintain incident response plans that include procedures for handling device DoS scenarios to minimize operational impact. These steps go beyond generic advice by focusing on access control, monitoring, and operational preparedness specific to this vulnerability's characteristics.

Description

In collectOps of AppOpsService.java, there is a possible way to cause permanent DoS due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…