Skip to main content
VulnerabilityPublished

CVE-2025-48524: 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
  • 13 – 16
4 affected builds
Fixed in–

AI-suggested

Organizations should prioritize updating Android devices to patched versions once available from Google or device manufacturers. Until patches are released, restricting installation of untrusted local applications and enforcing strict app permission policies can reduce the risk of exploitation. Mobile Device Management (MDM) solutions should be used to monitor device health and enforce security configurations. Network segmentation and limiting Wi-Fi access to trusted devices can minimize exposure. Additionally, educating users about the risks of installing unknown apps and monitoring for unusual device behavior can help detect potential exploitation attempts. For critical environments, consider temporarily disabling Wi-Fi or using alternative secure connectivity methods if feasible. Regularly reviewing device logs for crashes or abnormal Wi-Fi permission requests can aid early detection.

Description

In isSystem of WifiPermissionsUtil.java, there is a possible permission bypass due to a missing permission check. 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…