CVE-2025-48607VulnerabilityPublished 8 Dec 2025Updated 17 Dec 2025

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

Affects Google AndroidSource CVE Database V5

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.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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Dec 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Google Android	Affected =16 =15	Fixed in–

AI-suggested

To mitigate CVE-2025-48607, organizations should prioritize the following actions: 1) Monitor and restrict local privilege escalation paths on Android devices to prevent unauthorized local access. 2) Implement strict app vetting and control policies to avoid installation of malicious or untrusted applications that could exploit the vulnerability. 3) Once available, promptly apply official security patches from Google or device manufacturers addressing this vulnerability. 4) Employ mobile device management (MDM) solutions to enforce security policies, monitor app ops usage, and detect abnormal behavior indicative of exploitation attempts. 5) Educate users about the risks of installing untrusted apps and the importance of device security hygiene. 6) For critical environments, consider network segmentation and limiting device access to sensitive systems to reduce the impact of potential denial of service. 7) Engage in proactive vulnerability scanning and penetration testing focused on local privilege escalation and resource exhaustion scenarios on Android devices.

Description

In multiple locations, there is a possible way to create a large amount of app ops due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

Impact

For European organizations, this vulnerability poses a risk primarily to the availability of Android-based devices and services. Organizations relying on Android devices for critical business operations, mobile workforce management, or embedded systems could experience service disruptions if exploited. The denial of service could lead to operational downtime, reduced productivity, and potential loss of access to essential applications. While the vulnerability does not compromise data confidentiality or integrity, the availability impact could indirectly affect business continuity and user trust. Sectors with high dependency on mobile technology, such as finance, healthcare, and public services, may face heightened risks. Additionally, the requirement for local privileges means that the threat is more significant in environments where device access controls are weak or where malicious insiders or compromised apps are possible. The absence of user interaction for exploitation increases the risk of automated or stealthy attacks once local access is obtained.

Summary

CVE-2025-48607 is a vulnerability identified in Google Android versions 15 and 16 that allows a local attacker to cause a denial of service (DoS) condition by exploiting a logic error in the handling of app operations (app ops). The flaw enables the creation of an excessive number of app ops, which are internal Android constructs used to manage permissions and operations for apps. This excessive creation leads to resource exhaustion, potentially causing the system or affected services to become unresponsive or crash, thereby denying legitimate users access to device functionality. The vulnerability does not require any user interaction for exploitation, but it does require the attacker to have local privileges on the device, such as a malicious app or a compromised user account. The CVSS v3.1 base score is 5.5, reflecting a medium severity level, with the vector indicating local attack vector (AV:L), low attack complexity (AC:L), low privileges required (PR:L), no user interaction (UI:N), unchanged scope (S:U), no impact on confidentiality or integrity (C:N/I:N), but high impact on availability (A:H). There are no known exploits in the wild at the time of publication, and no patches have been linked yet, indicating that remediation may still be pending. The vulnerability could affect any Android device running the specified versions, including smartphones, tablets, and embedded Android systems. The root cause is a logic error in the code managing app ops, which could be addressed by limiting the creation rate or implementing proper cleanup mechanisms to prevent resource exhaustion.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Dec 2025, 16:50 UTC

Technical details

References

Community reviews

Related threats