# CVE-2026-59578: Google Pixel HWCodec Firmware buffer overflow in av1_encoder

Source: https://junglewise.ai/threats/cve-2026-59578-in-s-check-valid-tile-param-custom-tile-of-av1-encoder-there-is-a  
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-59578 · Severity: info · Published 2026-11-10

Google Pixel devices contain a video encoding firmware component (HWCodec) that is vulnerable to a buffer overflow in the AV1 encoder. An attacker with local access to the device could exploit this vulnerability to gain elevated privileges and execute code with system-level access. User interaction is required for exploitation.

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

## Quick answers

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

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

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

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

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

**Am I affected by CVE-2026-59578?** 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 security patch level 2026-11-05 or later

## Technical details

A non-heap buffer overflow exists in the s_check_valid_tile_param_custom_tile function of the av1_encoder component within HWCodec Firmware. The vulnerability requires local access and user interaction to trigger. Successful exploitation could lead to local privilege escalation and arbitrary code execution with elevated privileges.

## Affected products

- Google Pixel prior to 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)