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

AILast updated: 03/10/2026, 21:18:35 UTC

Technical Analysis

CVE-2026-0114 is a critical security vulnerability identified in the Android kernel, specifically within the modem component. The root cause is an out-of-bounds write triggered by an incorrect bounds check, which allows an attacker to overwrite memory outside the intended buffer. This memory corruption can be leveraged to execute arbitrary code remotely on the affected device. Notably, exploitation does not require any additional execution privileges or user interaction, significantly lowering the barrier for attackers. The vulnerability affects the Android kernel, which is a core component of the operating system responsible for managing hardware and system resources. Because the modem handles cellular communications, this flaw could be exploited remotely over the network, potentially by sending specially crafted data packets to the device's modem interface. Although no public exploits have been observed in the wild yet, the vulnerability's characteristics suggest it could be weaponized for widespread attacks. The absence of a CVSS score indicates that the vulnerability is newly disclosed, but its technical details and impact suggest a high severity level. The vulnerability was reserved in October 2025 and published in March 2026, indicating a recent discovery and disclosure timeline. The lack of patch links in the data suggests that fixes may still be pending or in the process of deployment by Google and device manufacturers.

Potential Impact

The impact of CVE-2026-0114 is severe for organizations and individuals relying on Android devices. Successful exploitation enables remote code execution at the kernel level, potentially allowing attackers to gain full control over the device, bypass security mechanisms, access sensitive data, install persistent malware, or disrupt device functionality. This could lead to data breaches, espionage, or denial of service conditions. Enterprises with large Android device fleets, especially those handling sensitive communications or critical infrastructure, face heightened risks. The vulnerability's exploitation without user interaction increases the likelihood of automated attacks and wormable malware propagation. Additionally, the modem's role in cellular communication means attackers could exploit devices remotely without physical proximity, expanding the attack surface. The broad deployment of Android worldwide amplifies the potential scale of impact, affecting consumers, businesses, and government agencies alike.

Mitigation Recommendations

To mitigate CVE-2026-0114, organizations and users should prioritize the following actions: 1) Monitor official Google security bulletins and device manufacturer advisories for patches addressing this vulnerability and apply updates immediately upon release. 2) Employ network-level protections such as firewalls and intrusion detection/prevention systems configured to detect and block anomalous modem-related traffic or malformed packets targeting cellular interfaces. 3) Implement endpoint detection and response (EDR) solutions capable of monitoring kernel-level anomalies and suspicious behaviors indicative of exploitation attempts. 4) Restrict unnecessary modem access and disable unused cellular interfaces where possible to reduce the attack surface. 5) For enterprise-managed devices, enforce strict device management policies ensuring timely patch deployment and security configuration compliance. 6) Educate users about the importance of installing updates promptly and maintaining device security hygiene. 7) Collaborate with mobile network operators to identify and mitigate suspicious traffic patterns that could indicate exploitation attempts. These measures, combined with rapid patching, will significantly reduce the risk posed by this vulnerability.

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/10/2026, 9:18:35 PM

Last updated: 3/14/2026, 3:01:10 AM

Views: 26

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 in Console -> Billing 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