# CVE-2026-0127: Google Pixel Modem out-of-bounds read in cn_NrmmDecoder.cpp

Source: https://junglewise.ai/threats/cve-2026-0127-google-pixel-modem-out-of-bounds-read-in-cn-nrmmdecoder-cpp  
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-0127 · Severity: info · CVSS 5.3 · Published 2026-06-16

A vulnerability exists in the modem component of Google Pixel devices. This component handles cellular communications, and a flaw in how it processes certain messages could allow a remote attacker to crash the communication processor. This would result in a loss of cellular connectivity (denial of service) for the user without requiring any interaction from them.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel Modem Devices with security patch levels before 2026-06-05.

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

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

**Am I affected by CVE-2026-0127?** 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

An out-of-bounds read vulnerability exists in the 'cn_NrmmDecoder.cpp' file within the 'NrmmMsgCodec::DecodeUPUTransparentContext' function of the Google Pixel modem firmware. The flaw is caused by memory corruption during the decoding of specific network messages. A remote attacker can exploit this over the network without any special privileges or user interaction. Successful exploitation results in a crash of the communication processor, leading to a denial of service (DoS). The issue is addressed in the June 2026 Pixel Security Bulletin with patch levels 2026-06-05 or later.

## Affected products

- Google Pixel Modem Devices with security patch levels before 2026-06-05

## Timeline

- 2026-06-16: advisory: NVD and Google Pixel Bulletin published
- 2026-06-05: patched: Security patch level date for fix

## 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 write remote code execution](https://junglewise.ai/threats/cve-2026-0139-google-pixel-modem-out-of-bounds-write-remote-code-execution)
- [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)