Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-48590: Denial of service in Google Android

0
Medium
VulnerabilityCVE-2025-48590cvecve-2025-48590
Published: Mon Dec 08 2025 (12/08/2025, 16:57:18 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In verifyAndGetBypass of AppOpsService.java, there is a possible method for a malicious app to prevent dialing emergency services under limited circumstances due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 12/17/2025, 16:47:53 UTC

Technical Analysis

CVE-2025-48590 is a denial of service vulnerability identified in Google Android operating system versions 13 through 16. The flaw exists in the verifyAndGetBypass method within AppOpsService.java, a component responsible for managing app operation permissions. A malicious application can exploit this vulnerability by causing resource exhaustion, which under certain limited conditions prevents the device from dialing emergency services. This attack does not require user interaction and can be executed with only limited privileges, meaning a low-privilege app installed on the device can trigger the denial of service. The vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption), indicating that the root cause is the improper handling of resource allocation leading to exhaustion. The impact is a local denial of service affecting the availability of emergency call functionality, a critical safety feature on mobile devices. The CVSS v3.1 score is 5.5 (medium severity), reflecting the lack of impact on confidentiality or integrity but a significant impact on availability. No patches have been linked yet, and no known exploits are reported in the wild, but the vulnerability poses a serious risk to users relying on Android devices for emergency communications. The issue highlights the importance of robust resource management in security-sensitive components of mobile operating systems.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the availability of emergency communication services on Android devices. Emergency call functionality is critical for personal safety, workplace health and safety compliance, and emergency response coordination. Disruption of this service could delay or prevent timely access to emergency responders, potentially leading to severe consequences in life-threatening situations. Organizations that provide mobile devices to employees, especially in sectors such as healthcare, public safety, transportation, and critical infrastructure, may face increased liability and operational risk. Additionally, the vulnerability could be exploited in targeted attacks to disrupt emergency services in specific locations or organizations. Although the attack requires local access and limited privileges, the widespread use of Android devices in Europe increases the attack surface. The lack of user interaction requirement further lowers the barrier for exploitation. Overall, the impact is primarily on availability, with potential indirect effects on organizational safety and compliance.

Mitigation Recommendations

1. Restrict installation of untrusted or potentially malicious applications by enforcing strict app store policies and using mobile device management (MDM) solutions to control app deployment. 2. Monitor and audit app permissions regularly to detect and remove apps with suspicious behavior or excessive privileges. 3. Educate users about the risks of installing apps from unknown sources and encourage the use of official app stores only. 4. Implement runtime monitoring tools that can detect abnormal resource consumption patterns indicative of exploitation attempts. 5. Prepare to deploy security patches promptly once Google releases an official fix for this vulnerability. 6. Consider deploying emergency call redundancy solutions, such as alternative communication apps or devices, especially in critical operational environments. 7. Coordinate with mobile carriers and emergency service providers to ensure rapid incident response if denial of service is detected. 8. Conduct regular security assessments and penetration testing focusing on mobile device security to identify and remediate similar vulnerabilities proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
google_android
Date Reserved
2025-05-22T18:11:57.728Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6937058152c2eb5957f2eebf

Added to database: 12/8/2025, 5:06:09 PM

Last enriched: 12/17/2025, 4:47:53 PM

Last updated: 2/4/2026, 7:20:37 AM

Views: 29

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats