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-0114: Remote code execution in Google Android

0
Critical
VulnerabilityCVE-2026-0114cvecve-2026-0114
Published: Tue Mar 10 2026 (03/10/2026, 20:46:43 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In Modem, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/18/2026, 19:21:15 UTC

Technical Analysis

CVE-2026-0114 is a critical security vulnerability identified in the Android kernel's modem component. The root cause is an out-of-bounds write resulting from an incorrect bounds check, classified under CWE-787. This flaw enables remote code execution (RCE) without requiring any user interaction or additional privileges, making it highly exploitable. The vulnerability affects the Android kernel, which is a core component of the operating system responsible for managing hardware interactions, including modem communications. An attacker exploiting this vulnerability can execute arbitrary code remotely, potentially gaining full control over the affected device. The CVSS v3.1 base score is 9.8, reflecting the vulnerability's critical severity with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and high impact on confidentiality (C:H), integrity (I:H), and availability (A:H). Although no public exploits are currently known, the vulnerability's nature and impact make it a prime target for attackers. The lack of available patches at the time of reporting increases the urgency for mitigation and monitoring. This vulnerability poses a significant threat to Android devices globally, especially those with modem components that handle cellular communications.

Potential Impact

The potential impact of CVE-2026-0114 is severe and wide-ranging. Successful exploitation allows attackers to execute arbitrary code remotely on affected Android devices, leading to full compromise of device confidentiality, integrity, and availability. This can result in unauthorized access to sensitive data, installation of persistent malware, disruption of device functionality, and potential use of compromised devices as footholds for further network attacks. Given the vulnerability resides in the modem component of the kernel, it could be exploited over cellular networks without user interaction, increasing the attack surface significantly. Organizations relying heavily on Android devices for communication, business operations, or as part of critical infrastructure face elevated risks. The absence of required privileges or user interaction lowers the barrier for exploitation, potentially enabling widespread attacks. This vulnerability could also undermine user trust in Android device security and impact sectors such as telecommunications, government, finance, and healthcare where mobile device security is paramount.

Mitigation Recommendations

To mitigate CVE-2026-0114, organizations and users should: 1) Monitor official Google and Android security advisories closely for patches and apply them immediately once available. 2) Employ network-level protections such as firewalls and intrusion detection/prevention systems to monitor and block suspicious modem-related traffic. 3) Limit exposure of vulnerable devices by restricting unnecessary cellular network access or using VPNs to secure communications. 4) Implement device management policies that enforce timely updates and restrict installation of untrusted applications. 5) Conduct regular security audits and vulnerability assessments on Android devices within the organization. 6) Educate users about the risks and encourage cautious behavior regarding device connectivity. 7) Collaborate with mobile carriers to identify and mitigate potential exploitation attempts at the network level. Since no patches are currently available, these proactive steps are critical to reduce the attack surface and delay or prevent exploitation.

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_Devices
Date Reserved
2025-10-23T08:43:09.817Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69b086492f860ef943bb98d7

Added to database: 3/10/2026, 8:59:53 PM

Last enriched: 3/18/2026, 7:21:15 PM

Last updated: 4/28/2026, 2:59:21 AM

Views: 197

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