# CVE-2026-0139: Google Pixel Modem out-of-bounds write remote code execution

Source: https://junglewise.ai/threats/cve-2026-0139-google-pixel-modem-out-of-bounds-write-remote-code-execution  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-16. Updated: 2026-06-16  
License: CC BY 4.0 with a link back

CVE-2026-0139 · Severity: info · CVSS 9.8 · Published 2026-06-16

A critical security vulnerability has been identified in the modem component of Google Pixel devices. The modem is responsible for cellular connectivity, and this flaw could allow a remote attacker to execute unauthorized code on the device without any user interaction. This could lead to a complete compromise of the device's communications and data security.

Technologies: [Google Pixel Modem](https://junglewise.ai/threats/technologies/pixel-modem). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-0139 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-0139 being exploited in the wild.

**How severe is CVE-2026-0139?** Informational severity, with a CVSS score of 9.8, published 16 June 2026.

**Which products and versions are affected?** Google Pixel Modem Devices updated before June 5, 2026 patch level.

**Is there a fix for CVE-2026-0139?** A patch was published on 2026-06-05: Security patch level 2026-06-05 or later required. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-0139 attacked?** It is attacked over the network, in device firmware.

**Am I affected by CVE-2026-0139?** Check whether you run Google Pixel Modem at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A remote code execution (RCE) vulnerability exists in the Modem component of Google Pixel devices. The flaw is rooted in an out-of-bounds (OOB) write condition caused by a missing bounds check during data processing. An attacker can exploit this over the network without requiring any special privileges or user interaction. Successful exploitation allows for arbitrary code execution within the context of the modem firmware. Google has addressed this issue in the June 2026 Pixel Security Bulletin; devices with a security patch level of 2026-06-05 or later are protected.

## Affected products

- Google Pixel Modem Devices updated before June 5, 2026 patch level

## Timeline

- 2026-06-16: disclosed
- 2026-06-05: patched: Security patch level 2026-06-05 or later required.

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-06-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-06-01)

## Related threats

- [Google Pixel Modem out-of-bounds write RCE](https://junglewise.ai/threats/cve-2026-0164-google-pixel-modem-out-of-bounds-write-rce)
- [Google Pixel Modem memory corruption in SIP REFER request](https://junglewise.ai/threats/cve-2026-0154-google-pixel-modem-memory-corruption-in-sip-refer-request)
- [Google Pixel Modem out-of-bounds read causing remote DoS](https://junglewise.ai/threats/cve-2026-0136-google-pixel-modem-out-of-bounds-read-causing-remote-dos)
- [Google Pixel Modem out-of-bounds read leading to RCE](https://junglewise.ai/threats/cve-2026-0135-google-pixel-modem-out-of-bounds-read-leading-to-rce)
- [Google Pixel Modem heap buffer overflow RCE](https://junglewise.ai/threats/cve-2026-0132-google-pixel-modem-heap-buffer-overflow-rce)