Quick answers
- Is CVE-2026-0140 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0140 being exploited in the wild.
- How severe is CVE-2026-0140?
- Informational severity, with a CVSS score of 6.5, published 16 June 2026.
- Which products and versions are affected?
- Google Libpixelimsmedia Android devices with security patch levels before 2026-06-05.
- Is there a fix for CVE-2026-0140?
- A patch was published on 2026-06-05: Security patch level date addressing the issue. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0140 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-0140?
- 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 library within the RtpPacket::decodePacket function. The flaw is caused by an integer overflow during the processing of RTP packets, which results in an out-of-bounds read. An attacker can exploit this to disclose sensitive information from the process memory. While the attack vector is remote, exploitation requires user interaction. The issue was addressed in the June 2026 Pixel Update Bulletin, with the fix included in security patch levels 2026-06-05 or later.
Affected products
- Google libpixelimsmedia Android devices with security patch levels before 2026-06-05
Timeline
- 2026-06-16: advisory: Initial publication of the Pixel Update Bulletin and NVD entry.
- 2026-06-05: patched: Security patch level date addressing the issue.