# CVE-2026-0157: Google libpixelimsmedia out-of-bounds read in RtcpHeader::decodeRtcpHeader

Source: https://junglewise.ai/threats/cve-2026-0157-google-libpixelimsmedia-out-of-bounds-read-in-rtcpheader  
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-0157 · Severity: info · CVSS 7.5 · Published 2026-06-16

A security vulnerability exists in a media processing library used by Google Pixel devices. This component handles real-time communication protocols, and the flaw allows a remote attacker to access sensitive information from the device's memory without any user interaction. This could lead to the exposure of private data or system information that could be used in further attacks.

Technologies: [Google Libpixelimsmedia](https://junglewise.ai/threats/technologies/libpixelimsmedia). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

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

**Which products and versions are affected?** Google Libpixelimsmedia Android versions prior to 2026-06-05 patch level.

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

**How is CVE-2026-0157 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-0157?** Check whether you run Google Libpixelimsmedia 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 (OOB) read vulnerability exists in the 'RtcpHeader::decodeRtcpHeader' function within the 'libpixelimsmedia' library on Google Pixel devices. The flaw is caused by a missing bounds check during the decoding of RTCP (Real-time Control Protocol) headers. A remote, unauthenticated attacker can exploit this by sending specially crafted network packets to trigger an out-of-bounds memory access. Successful exploitation results in the disclosure of sensitive information from the process memory. The issue is addressed in the June 2026 Pixel security update (patch level 2026-06-05).

## Affected products

- Google libpixelimsmedia Android versions prior to 2026-06-05 patch level

## Timeline

- 2026-06-16: disclosed
- 2026-06-16: advisory
- 2026-06-05: patched

## 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 libpixelimsmedia out-of-bounds read in RTCP packet decoder](https://junglewise.ai/threats/cve-2026-0165-google-libpixelimsmedia-out-of-bounds-read-in-rtcp-packet-decoder)
- [Google libpixelimsmedia out-of-bounds read in ReadByteBuffer](https://junglewise.ai/threats/cve-2026-0155-google-libpixelimsmedia-out-of-bounds-read-in-readbytebuffer)
- [Google libpixelimsmedia integer overflow in RtpPacket::decodePacket](https://junglewise.ai/threats/cve-2026-0140-google-libpixelimsmedia-integer-overflow-in-rtppacket-decodepacket)
- [Google libpixelimsmedia integer overflow in decodeRtcpFbPacket](https://junglewise.ai/threats/cve-2026-0128-google-libpixelimsmedia-integer-overflow-in-decodertcpfbpacket)