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-36889: Information disclosure in Google Android

0
Medium
VulnerabilityCVE-2025-36889cvecve-2025-36889
Published: Thu Dec 11 2025 (12/11/2025, 19:35:30 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In onCreateTasks of CameraActivity.java, there is a possible permission bypass due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 12/11/2025, 20:16:13 UTC

Technical Analysis

CVE-2025-36889 is a vulnerability discovered in the Android kernel, specifically within the CameraActivity.java component's onCreateTasks method. The flaw is characterized as a permission bypass caused by a confused deputy scenario, where the system component inadvertently grants access to information without proper authorization checks. This results in local information disclosure, meaning an attacker with local access to the device can retrieve sensitive data without needing elevated privileges or user interaction. The vulnerability does not require the attacker to execute code with higher privileges or trick the user, increasing the risk of unnoticed exploitation. The affected component is part of the Android kernel, which underpins the operating system's core functions, making this a significant security concern. Although no public exploits have been reported yet, the nature of the vulnerability suggests that attackers could leverage it to access confidential information stored or processed on the device. This could include personal data, authentication tokens, or other sensitive material accessible via the camera subsystem or related processes. The lack of a CVSS score indicates that the vulnerability is newly published and pending further assessment. However, the technical details imply a serious risk due to the combination of no required privileges, no user interaction, and kernel-level impact.

Potential Impact

For European organizations, the primary impact of CVE-2025-36889 lies in the potential unauthorized disclosure of sensitive information from Android devices used within corporate environments. This could compromise personal data of employees, intellectual property, or confidential communications, especially in sectors relying on mobile device security such as finance, healthcare, and government. The vulnerability's kernel-level nature means that it could affect a wide range of Android devices, increasing the attack surface. Since exploitation does not require elevated privileges or user interaction, attackers with local access—such as through physical device theft or insider threats—could exploit this flaw stealthily. This undermines device trustworthiness and could lead to compliance violations under GDPR if personal data is exposed. Additionally, organizations with Bring Your Own Device (BYOD) policies may face increased risk due to diverse device management challenges. The absence of known exploits in the wild currently limits immediate risk, but the potential for future weaponization remains significant.

Mitigation Recommendations

To mitigate CVE-2025-36889, European organizations should prioritize the following actions: 1) Monitor official Google security advisories and Android security bulletins for patches addressing this vulnerability and apply updates promptly once available. 2) Enforce strict device management policies, including restricting physical access to devices and employing mobile device management (MDM) solutions to control application permissions and monitor device integrity. 3) Limit the use of sensitive applications on vulnerable devices and segregate sensitive data access to minimize exposure. 4) Educate employees on the risks of device theft and insider threats, emphasizing secure handling of corporate devices. 5) Implement endpoint detection and response (EDR) solutions capable of identifying anomalous local access attempts or suspicious activity related to camera or kernel components. 6) Consider disabling or restricting camera functionality on devices where it is not essential, reducing the attack surface. 7) Regularly audit device security posture and compliance with organizational policies to detect potential exploitation attempts early. These measures, combined with timely patching, will reduce the risk posed by this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Google_Devices
Date Reserved
2025-04-16T00:33:09.030Z
Cvss Version
null
State
PUBLISHED

Threat ID: 693b21637d4c6f31f7c35302

Added to database: 12/11/2025, 7:54:11 PM

Last enriched: 12/11/2025, 8:16:13 PM

Last updated: 12/12/2025, 3:07:42 AM

Views: 6

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