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