# CVE-2026-0131: Google Pixel libpixelimsmedia integer overflow in RtpPacket::decodePacket

Source: https://junglewise.ai/threats/cve-2026-0131-google-pixel-libpixelimsmedia-integer-overflow-in-rtppacket  
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-0131 · Severity: info · CVSS 7.8 · Published 2026-06-16

A security vulnerability exists in the media handling component of Google Pixel devices. This flaw could allow a local attacker to gain elevated system privileges, potentially leading to unauthorized access to sensitive data or control over device functions. Exploitation requires a user to interact with a malicious file or application.

Technologies: [Google Pixel Firmware](https://junglewise.ai/threats/technologies/pixel-firmware). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

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

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

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

**How is CVE-2026-0131 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-0131?** Check whether you run Google Pixel Firmware. 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 integer overflow vulnerability exists within the 'RtpPacket::decodePacket' function of the 'libpixelimsmedia' component in Google Pixel devices. This flaw leads to an out-of-bounds memory access when processing specially crafted Real-time Transport Protocol (RTP) packets. A local attacker can exploit this to achieve escalation of privilege (EoP) without requiring prior elevated permissions, though user interaction is a prerequisite for the attack. The issue is addressed in the June 2026 Pixel security update (patch level 2026-06-05).

## Affected products

- Google Pixel Firmware prior to 2026-06-05 patch level

## Timeline

- 2026-06-16: disclosed
- 2026-06-05: patched: Security patch level date

## 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 Pixel firmware heap buffer overflow in CLDMA audio processing](https://junglewise.ai/threats/cve-2026-59601-in-calculatesamplerate-of-cldma-alcedo-cc-there-is-a-possible)
- [Google Pixel firmware out-of-bounds write in NCI command handler](https://junglewise.ai/threats/cve-2026-59587-in-stpropnci-prop-st-build-set-custom-polling-cmd-of-stpropnci)
- [Google Pixel firmware out of bounds read/write in log formatting](https://junglewise.ai/threats/cve-2026-59574-in-notifypollingloopframes-of-hal-fwlog-cc-there-is-a-possible)
- [Google Pixel firmware information disclosure on warm reset](https://junglewise.ai/threats/cve-2026-58808-in-multiple-locations-there-is-a-possible-way-to-dump-secure)
- [Google Pixel firmware memory bounds check in secure boot](https://junglewise.ai/threats/cve-2026-58805-in-multiple-locations-there-is-a-possible-way-to-zero-arbitrary)