# CVE-2026-56974: Google Pixel libpixelimsmedia out-of-bounds write in AudioRtpPayloadEncoderNode

Source: https://junglewise.ai/threats/cve-2026-56974-google-pixel-libpixelimsmedia-out-of-bounds-write-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-56974 · Severity: high · CVSS 8.8 · Published 2026-09-15

Google Pixel devices contain a vulnerable audio processing library (libpixelimsmedia) used to encode real-time multimedia streams. A flaw in the AudioRtpPayloadEncoderNode component allows an attacker to write data beyond allocated memory boundaries through improper input validation. An attacker can exploit this to execute arbitrary code on affected devices with no additional privileges, though user interaction is required to trigger the vulnerability.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android), [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

**How severe is CVE-2026-56974?** High severity, with a CVSS score of 8.8, published 15 September 2026.

**Which products and versions are affected?** Google Pixel Devices Pre-2026-09-05 patch level.

**Is there a fix for CVE-2026-56974?** A patch was published on 2026-09-05: Addressed in 2026-09-05 patch level and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-56974 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-56974?** Check whether you run Google Android or Google Pixel Devices 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

The vulnerability is an out-of-bounds write caused by improper input validation in the AudioRtpPayloadEncoderNode.cpp file within Google's libpixelimsmedia library. The flaw allows an attacker to write to memory outside the intended buffer boundaries, potentially enabling code execution. The vulnerability requires user interaction to exploit (e.g., processing a specially crafted audio stream), but once triggered, permits remote code execution without requiring elevated privileges. The Pixel Update Bulletin for September 2026 (patch level 2026-09-05 or later) addresses this issue.

## Affected products

- Google Pixel devices Pre-2026-09-05 patch level

## Timeline

- 2026-09-15: disclosed: Published in Pixel Update Bulletin
- 2026-09-05: patched: Addressed in 2026-09-05 patch level and later

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)