CVE-2026-0135
Description
A missing bounds check in the Pixel Modem component leads to an out-of-bounds read, enabling remote code execution without user interaction.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A missing bounds check in the Pixel Modem component leads to an out-of-bounds read, enabling remote code execution without user interaction.
Vulnerability
In the Modem component of Google Pixel devices, an out-of-bounds read vulnerability exists due to a missing bounds check. This flaw, identified as CVE-2026-0135, is present in firmware versions prior to the 2026-06-05 security patch level. The affected component is the Modem, as listed in the Pixel Update Bulletin [1].
Exploitation
An attacker can exploit this vulnerability remotely without any user interaction and without requiring additional execution privileges. The exact network vector is not detailed in the available references, but the Modem's exposure to baseband messages makes it likely that the attack is carried out over the air via crafted baseband signaling. No authentication or physical proximity is needed beyond standard network access [1].
Impact
Successful exploitation allows an attacker to achieve remote code execution (RCE) on the device's Modem processor. Since the Modem runs at a privileged level, this could lead to further compromise of the device. The severity is rated Critical [1].
Mitigation
Google addressed this vulnerability in the June 2026 Pixel Update Bulletin with a security patch level of 2026-06-05 or later. Users should apply the over-the-air (OTA) update to receive the fix. No workarounds have been published; updating to the latest security patch is the recommended mitigation [1].
AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.