# CVE-2026-59616: Google Pixel HWCodec Firmware buffer overflow in prev_run_vcore

Source: https://junglewise.ai/threats/cve-2026-59616-in-prev-run-vcore-of-hwcodec-firmware-there-is-a-possible-non  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-59616 · Severity: info · Published 2026-11-10

Google Pixel devices contain a buffer overflow vulnerability in the hardware codec firmware component that allows local code execution with elevated privileges. An attacker with local access to the device can exploit this to gain system-level control, potentially exposing encrypted data and enabling malware installation.

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

## Quick answers

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

**How severe is CVE-2026-59616?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel Before 2026-11-05 security patch level.

**Is there a fix for CVE-2026-59616?** Yes: fixed in Pixel devices with 2026-11-05 or later security patch level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-59616 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-59616?** Check whether you run Google Pixel 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.

## How to fix

- Fixed in Pixel devices with 2026-11-05 or later security patch level

## Technical details

A non-heap buffer overflow exists in the prev_run_vcore function of hwcodec_firmware, allowing local privilege escalation. The vulnerability requires execution privileges and user interaction for exploitation. An attacker can trigger this overflow to execute arbitrary code at a higher privilege level than the application.

## Affected products

- Google Pixel Before 2026-11-05 security patch level

## Timeline

- 2026-11-10: disclosed

## References

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

## Related threats

- [Google Pixel coprocessor memory privilege escalation](https://junglewise.ai/threats/cve-2026-95404-in-multiple-locations-there-is-a-possible-way-to-modify)
- [Google Pixel shared memory bitmap out-of-bounds write](https://junglewise.ai/threats/cve-2026-95403-in-multiple-locations-there-is-a-possible-way-to-trigger-an-out)
- [Google Pixel HWCodec buffer overflow in HEVC decoder](https://junglewise.ai/threats/cve-2026-95402-in-slice-header-of-hevc-decoder-there-is-a-possible-non-heap)
- [Google Pixel hevc_decoder buffer overflow](https://junglewise.ai/threats/cve-2026-95401-in-knee-function-info-of-hevc-decoder-there-is-a-possible-non)
- [Google Pixel FaceAuth race condition in biometric enrollment](https://junglewise.ai/threats/cve-2026-95399-in-multiple-functions-of-face-status-h-there-is-a-possible-way-to)