Quick answers
- Is CVE-2026-0128 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0128 being exploited in the wild.
- How severe is CVE-2026-0128?
- Informational severity, with a CVSS score of 7.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-0128?
- A patch was published on 2026-06-05: Security patch level 2026-06-05 or later addresses this issue. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0128 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-0128?
- 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
A vulnerability exists in the libpixelimsmedia component of Google Pixel devices within the RtcpFbPacket::decodeRtcpFbPacket function. The flaw is caused by an integer overflow that leads to an out-of-bounds read during the processing of RTCP Feedback packets. An unauthenticated remote attacker can exploit this by inducing a user to process a malicious packet, potentially resulting in the disclosure of sensitive information from the process memory. While the NVD entry lists the severity as 'info' (awaiting enrichment), the primary vendor (Google) classifies this as 'High' severity (ID/Information Disclosure). A patch is available in the June 2026 Pixel Security Bulletin.
Affected products
- Google libpixelimsmedia Android Pixel devices prior to 2026-06-05 patch level
Timeline
- 2026-06-16: disclosed
- 2026-06-16: advisory
- 2026-06-05: patched: Security patch level 2026-06-05 or later addresses this issue.