Skip to main content
CVE-2025-26456VulnerabilityPublished Updated

CVE-2025-26456: Google Android · Denial of service

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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: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 2026-10-25.

What to do

Affected software

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

AI-suggested

To mitigate CVE-2025-26456, organizations should implement the following specific measures: 1) Restrict installation of untrusted or third-party applications by enforcing strict app vetting and using mobile device management (MDM) solutions to control app permissions and sources. 2) Limit local access to devices by enforcing strong physical security controls and user authentication to prevent unauthorized local exploitation. 3) Monitor device behavior for signs of system server crashes or instability that could indicate exploitation attempts. 4) Encourage users to reboot devices if instability occurs as a temporary recovery measure. 5) Stay informed about official Google security advisories and apply patches promptly once available. 6) Consider deploying endpoint detection and response (EDR) tools capable of detecting anomalous local activity related to system server crashes. 7) For high-risk environments, evaluate the feasibility of restricting Android versions to those not affected or using custom security-hardened builds. These targeted actions go beyond generic advice by focusing on controlling local access, monitoring for specific crash symptoms, and preparing for timely patch deployment.

Description

In multiple functions of DexUseManagerLocal.java, there is a possible way to crash system server due to a logic error in the code. This could lead to local permanent denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…