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

0
Medium
VulnerabilityCVE-2026-0005cvecve-2026-0005
Published: Mon Mar 02 2026 (03/02/2026, 18:42:31 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In onServiceDisconnected of KeyguardServiceDelegate.java, there is a possible partial bypass of app pinning allowing limited interaction with other apps without knowing the LSKF due to a missing permission check. This could lead to local information disclosure where the extent of interaction and impact is app-dependent with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/10/2026, 16:53:07 UTC

Technical Analysis

CVE-2026-0005 is a vulnerability identified in Google Android operating system versions 14, 15, and 16, specifically within the KeyguardServiceDelegate.java component. The issue occurs in the onServiceDisconnected method, where a missing permission check allows a partial bypass of app pinning security controls. App pinning is designed to restrict user interaction to a single app, preventing switching to other apps without proper authentication, typically requiring the lock screen keyguard (LSKF). Due to the missing permission verification, an attacker with local access can interact with other apps to a limited extent without knowing the LSKF, effectively bypassing intended restrictions. This interaction does not grant elevated execution privileges but can lead to information disclosure, as the attacker may access data or functionality within other apps depending on their design and permissions. The vulnerability does not require user interaction or authentication, making it easier to exploit for local attackers. The CVSS v3.1 score is 6.2, reflecting a medium severity with high confidentiality impact but no integrity or availability impact. No known exploits have been reported in the wild, and no official patches are currently linked, indicating the need for vigilance and timely updates once available.

Potential Impact

The primary impact of CVE-2026-0005 is local information disclosure on affected Android devices. Attackers with physical or local access can partially bypass app pinning, potentially accessing sensitive data from other apps without authentication. This could lead to leakage of personal or corporate data, undermining user privacy and security. Because the vulnerability does not grant additional execution privileges or affect system integrity or availability, it is less likely to be used for privilege escalation or denial of service attacks. However, in environments where devices are shared or at risk of unauthorized local access, such as corporate or government settings, the vulnerability could facilitate data leakage or unauthorized information gathering. The lack of user interaction requirement increases the risk of stealthy exploitation. Organizations relying on Android devices for sensitive operations should consider this vulnerability a moderate risk, especially where physical device security is limited.

Mitigation Recommendations

To mitigate CVE-2026-0005, organizations should implement strict physical security controls to prevent unauthorized local access to Android devices running versions 14, 15, or 16. Until official patches are released, disabling app pinning or limiting its use in high-risk environments may reduce exposure. Employing device management solutions to enforce strong lock screen policies and restricting installation of untrusted apps can minimize attack vectors. Monitoring device logs for unusual app interactions may help detect exploitation attempts. Once Google releases patches, prompt application of updates is critical. Additionally, educating users about the risks of leaving devices unattended and encouraging the use of full-disk encryption can further protect sensitive data. Developers should review app permissions and design to limit sensitive data exposure in case of partial app pinning bypass.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
google_android
Date Reserved
2025-10-15T15:38:07.612Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a5db7ed1a09e29cb1cb97c

Added to database: 3/2/2026, 6:48:30 PM

Last enriched: 3/10/2026, 4:53:07 PM

Last updated: 4/17/2026, 10:28:44 AM

Views: 143

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 more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses