VulnerabilityPublished 2 Mar 2026Updated 6 Mar 2026

CVE-2026-0024: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.0 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

4.0Medium

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: 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: 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: 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 2 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 29 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 14 – 16-qpr2 4 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2026-0024, organizations and users should: 1) Monitor official Google Android security bulletins and update devices promptly once patches are released for the affected versions (14 through 16-qpr2). 2) Restrict physical and local access to devices, especially in sensitive environments, to prevent unauthorized local exploitation. 3) Employ mobile device management (MDM) solutions to enforce application permissions and limit installation of untrusted local apps that could exploit this vulnerability. 4) Consider disabling or restricting access to media content providers or content resolver interfaces for untrusted applications where feasible. 5) Audit installed applications for unnecessary permissions and remove or restrict apps that could leverage local access to extract media location data. 6) Use encryption and secure storage mechanisms for sensitive media files to reduce exposure. 7) Educate users on the risks of sharing devices or installing untrusted apps that may exploit local vulnerabilities. These steps go beyond generic advice by focusing on controlling local access and application permissions, which are critical given the local attack vector and no privilege requirements.

Description

In isRedactionNeededForOpenViaContentResolver of MediaProvider.java, there is a possible way to reveal the location of media due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Impact

The primary impact of CVE-2026-0024 is the unauthorized disclosure of location information embedded in media files on affected Android devices. This can compromise user privacy by revealing sensitive location data without user consent. For organizations, especially those handling sensitive or classified information on Android devices, this vulnerability could lead to inadvertent leakage of location data, potentially exposing operational details or user whereabouts. Although the vulnerability does not allow modification or deletion of data (integrity and availability are unaffected), the confidentiality breach could be exploited for targeted surveillance, profiling, or reconnaissance by local attackers or malicious insiders. The lack of required privileges and user interaction lowers the barrier for exploitation, increasing the risk in environments where devices are shared or physically accessible by untrusted parties. However, since exploitation requires local access, remote attackers are not directly impacted. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future abuse once proof-of-concept code becomes available.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

source.android.com/docs/security/bulletin/2026/2026-03-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 16:57 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats