VulnerabilityPublished 11 Dec 2025

CVE-2025-36889: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.07% 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:H/I:N/A:N

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

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.

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.

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.

CWE-441Unintended Proxy or Intermediary ('Confused Deputy') (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.
Architecture and Design
Enforce the use of strong mutual authentication mechanism between the two parties.
Architecture and Design
Whenever a product is an intermediary or proxy for transactions between two other components, the proxy core should not drop the identity of the initiator of the transaction. The immutability of the identity of the initiator must be maintained and should be forwarded all the way to the target.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
XML Routing Detour Attacks (opens in a new tab)
Transparent Proxy Abuse (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

source.android.com/security/bulletin/pixel/2025-12-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Dec 2025, 20:16 UTC

WeaknessesCWE-441

Technical details

References

Community reviews

Related threats