VulnerabilityPublished 10 Mar 2026

CVE-2026-0115: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.1 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

2.1Low

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

EPSS: 0.09% 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:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
GoogleAndroid	Affected =Android kernel	Fixed in–

AI-suggested

To mitigate CVE-2026-0115, organizations and users should prioritize installing security updates and patches provided by Google and device manufacturers as soon as they become available. Since the vulnerability resides in the Android kernel's TEE implementation, firmware and OS updates are critical. Until patches are deployed, users should exercise caution with unsolicited messages, links, or applications that require interaction, as these could be vectors for triggering the side-channel leak. Enterprises should implement mobile device management (MDM) policies to control app installations and enforce security configurations. Developers and security teams should monitor official advisories from Google and Android security bulletins for updates and guidance. Additionally, employing behavioral detection tools that monitor unusual app or system behavior may help identify exploitation attempts. For high-security environments, consider restricting the use of vulnerable devices or isolating sensitive operations to hardware or software platforms not affected by this vulnerability. Finally, educating users about social engineering risks and safe mobile practices can reduce the likelihood of successful exploitation.

Description

In Trusted Execution Environment, there is a possible key leak due to side channel information disclosure. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Impact

The primary impact of CVE-2026-0115 is the compromise of confidentiality within the Trusted Execution Environment on Android devices. If exploited, attackers could obtain cryptographic keys or sensitive data, potentially undermining the security of encrypted communications, authentication tokens, or digital rights management (DRM) protections. This could lead to unauthorized data access, identity theft, or bypassing security controls that rely on TEE protections. Since the TEE is designed to protect highly sensitive operations, the leakage of keys could have cascading effects on device security and user privacy. The requirement for user interaction limits the ease of exploitation but does not eliminate risk, especially in environments where users may be targeted with phishing or social engineering attacks. The vulnerability does not affect system availability or integrity directly but could facilitate further attacks if keys are compromised. Organizations relying on Android devices for secure communications, mobile payments, or confidential data processing are particularly at risk. The widespread use of Android globally means the potential impact is extensive, affecting both consumers and enterprises.

CWE-1300Improper Protection of Physical Side Channels (opens in a new tab)
Base weakness
The device does not contain sufficient protection mechanisms to prevent physical side channels from exposing sensitive information due to patterns in physically observable phenomena such as variations in power consumption, electromagnetic emissions (EME), or acoustic emissions.
Architecture and Design
Apply blinding or masking techniques to implementations of cryptographic algorithms.
Implementation
Add shielding or tamper-resistant protections to the device to increase the difficulty of obtaining measurements of the side-channel.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Black Box Reverse Engineering (opens in a new tab)
Eavesdropping on a Monitor (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 21:18 UTC

WeaknessesCWE-1300

Technical details

References

Community reviews

Related threats