Skip to main content
VulnerabilityPublished

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

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 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 21% 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 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 specific mitigation steps: 1) Immediate inventory and identification of Android devices running versions 13, 14, or 15, focusing on those with elevated privileges or used in sensitive roles. 2) Monitor official Google security advisories closely for patches or updates addressing CVE-2025-48534 and apply them promptly once available. 3) Implement strict privilege management policies on Android devices to minimize the number of apps or processes with system execution privileges, reducing the attack surface. 4) Employ mobile device management (MDM) solutions to enforce security policies, detect anomalous behavior indicative of exploitation attempts, and remotely isolate or remediate compromised devices. 5) Enhance network segmentation and restrict network access to Android devices to limit exposure to potential attackers. 6) Conduct targeted security awareness and training for IT staff to recognize signs of exploitation and respond effectively. 7) Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of monitoring Android device behavior for exploitation attempts. These measures go beyond generic patching advice by focusing on privilege minimization, proactive monitoring, and rapid response capabilities.

Description

In getDefaultCBRPackageName of CellBroadcastHandler.java, there is a possible escalation of privilege due to a logic error in the code. This could lead to local denial of service with System execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…