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-26463: Denial of service in Google Android

0
Medium
VulnerabilityCVE-2025-26463cvecve-2025-26463
Published: Thu Sep 04 2025 (09/04/2025, 17:15:07 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In allowPackageAccess of multiple files, resource exhaustion is possible when repeatedly adding allowed packages. This could lead to a local persistent denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 09/11/2025, 20:20:41 UTC

Technical Analysis

CVE-2025-26463 is a vulnerability identified in the Android operating system, specifically affecting versions 13, 14, and 15. The flaw exists in the allowPackageAccess functionality, where repeated additions of allowed packages can lead to resource exhaustion. This resource exhaustion manifests as a denial of service (DoS) condition that is local and persistent, meaning the affected device can become unresponsive or severely degraded in performance until a restart or remediation occurs. Notably, exploitation of this vulnerability does not require user interaction, nor does it require elevated privileges beyond local access, making it easier for an attacker with limited access to cause disruption. The vulnerability is categorized under CWE-400, which relates to uncontrolled resource consumption, indicating that the root cause is the system's failure to properly limit or manage resource allocation when handling allowed packages. The CVSS v3.1 base score is 5.5 (medium severity), reflecting that while the impact is significant in terms of availability (denial of service), there is no impact on confidentiality or integrity, and the attack vector is local with low complexity and low privileges required. There are no known exploits in the wild at this time, and no official patches have been linked yet, which suggests that affected organizations should be vigilant and prepare to apply updates once available.

Potential Impact

For European organizations, the impact of CVE-2025-26463 primarily concerns availability of Android devices used within corporate environments. Many enterprises rely on Android smartphones and tablets for communication, mobile workforce management, and access to corporate resources. A persistent denial of service on these devices could disrupt business operations, delay communications, and reduce productivity. Since exploitation does not require user interaction, an insider threat or malware with local access could trigger the DoS condition, potentially as part of a broader attack or sabotage. Critical sectors such as finance, healthcare, and government agencies that depend on mobile devices for secure and timely operations could face operational risks. Additionally, organizations with Bring Your Own Device (BYOD) policies may see increased exposure if personal devices are compromised or used as attack vectors. Although the vulnerability does not allow data theft or system compromise, the disruption of availability can have cascading effects on incident response, emergency communications, and service delivery.

Mitigation Recommendations

To mitigate CVE-2025-26463, European organizations should implement the following specific measures: 1) Monitor and restrict local access to Android devices, ensuring that only trusted users and applications can interact with package management functions. 2) Employ mobile device management (MDM) solutions to enforce security policies that limit the installation or modification of allowed packages, and to detect abnormal behavior indicative of resource exhaustion attempts. 3) Educate users about the risks of installing untrusted applications or granting unnecessary permissions that could facilitate local exploitation. 4) Prepare for timely deployment of patches from Google by establishing rapid update testing and rollout procedures for Android devices in the enterprise. 5) Consider implementing device usage policies that restrict the use of vulnerable Android versions (13, 14, 15) in critical roles until patches are available. 6) Use endpoint detection and response (EDR) tools capable of identifying anomalous resource consumption patterns on mobile devices. 7) Regularly audit device logs for signs of repeated package additions or other suspicious activities that could indicate attempts to exploit this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
google_android
Date Reserved
2025-02-10T18:29:54.133Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68b9ccbad6fd7c5a76c5d8b3

Added to database: 9/4/2025, 5:30:34 PM

Last enriched: 9/11/2025, 8:20:41 PM

Last updated: 10/17/2025, 4:52:18 AM

Views: 32

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats