Quick answers
- Is CVE-2026-0165 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0165 being exploited in the wild.
- How severe is CVE-2026-0165?
- Informational severity, with a CVSS score of 6.5, published 16 June 2026.
- Which products and versions are affected?
- Google Libpixelimsmedia Android Pixel devices prior to 2026-06-05 patch level.
- Is there a fix for CVE-2026-0165?
- A patch was published on 2026-06-05: Security patch level released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0165 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-0165?
- 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 read vulnerability exists in the RTCP (Real-time Transport Control Protocol) packet decoder within the libpixelimsmedia library on Google Pixel devices. The flaw is caused by missing bounds checks in several decoding functions. A remote attacker can exploit this by sending malformed RTCP packets, which, upon processing, allows for the disclosure of sensitive information from the process memory. Exploitation requires user interaction, likely in the context of a multimedia session or call. The issue is addressed in the June 2026 Pixel Security Bulletin with patch levels 2026-06-05 or later.
Affected products
- Google libpixelimsmedia Android Pixel devices prior to 2026-06-05 patch level
Timeline
- 2026-06-16: disclosed: Vulnerability details published in Google Pixel Update Bulletin
- 2026-06-05: patched: Security patch level released to address the issue