Skip to main content
VulnerabilityPublished Updated

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

Affects Google AndroidSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 06:59 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 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • 14 – 16-qpr2
4 affected builds
Fixed in–

AI-suggested

  1. Monitor official Google Android security bulletins and promptly apply patches or security updates once they become available for the affected versions (14, 15, 16, 16-qpr2).
  2. Restrict local access to devices by enforcing strong physical security controls and limiting user privileges to reduce the risk of local exploitation.
  3. Employ mobile device management (MDM) solutions to enforce security policies, monitor device health, and detect abnormal behavior indicative of DoS conditions.
  4. Educate users about the risks of installing untrusted applications or granting unnecessary permissions that could facilitate local attacks.
  5. Implement runtime protections such as application sandboxing and exploit mitigation techniques to reduce the impact of improper input validation.
  6. In environments with shared devices, enforce session management and user isolation to prevent unauthorized local access.
  7. Regularly back up critical data to mitigate operational impact in case devices become unresponsive due to exploitation.
  8. Use security monitoring tools to detect repeated crashes or service interruptions that may indicate exploitation attempts.
  9. Consider upgrading to newer Android versions beyond 16-qpr2 when available, as they may include fixes or improved security controls.

Description

In multiple locations, there is a possible persistent denial of service 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…