CVE-2025-26432: Google Android · Denial of Service
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Android | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Monitor for official security advisories and patches from Google and Android device manufacturers, and apply updates promptly once available. 2) Implement strict access controls and device usage policies to limit local access to Android devices, reducing the risk of exploitation by unauthorized users. 3) Employ mobile device management (MDM) solutions to enforce security configurations, detect anomalous device behavior indicative of DoS conditions, and remotely isolate or remediate affected devices. 4) Educate employees about the risks of local device access and encourage secure handling of mobile devices to prevent unauthorized physical or logical access. 5) Consider deploying endpoint detection and response (EDR) tools capable of monitoring for signs of persistent DoS or abnormal system crashes on mobile devices. 6) For critical environments, evaluate the feasibility of restricting Android 15 device usage until patches are available or alternative secure devices are deployed. 7) Establish incident response procedures specifically addressing mobile device DoS scenarios to minimize downtime and restore availability quickly.
Description
In multiple locations, there is a possible way to persistently DoS the device due to a missing length check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.