CVE-2026-59635: Google Pixel HWCodec buffer overflow in AVC decoder

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

Google Pixel devices include hardware video decoder firmware that processes video streams. A buffer overflow vulnerability in the AVC decoder's cpb_cnt field could allow a local attacker with access to media playback to escalate privileges and execute arbitrary code on the device.

Technologies: Google Pixel. Vendors: Google.

Quick answers

Is CVE-2026-59635 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-59635 being exploited in the wild.
How severe is CVE-2026-59635?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Pixel unspecified.
Is there a fix for CVE-2026-59635?
Yes: fixed in Pixel firmware with Android 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-59635 attacked?
It is attacked with local access, in device firmware.
Am I affected by CVE-2026-59635?
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 firmware with Android security patch level 2026-11-05 or later

Technical details

A non-heap buffer overflow exists in the cpb_cnt component of the AVC decoder firmware. The vulnerability requires user interaction (video playback) and local execution privileges to trigger. Successful exploitation grants privilege escalation on the affected Pixel device. Google patched this issue in the November 2026 security update (2026-11-05 patch level).

Affected products

  • Google Pixel unspecified

Timeline

  • 2026-11-10: disclosed
  • 2026-11-05: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.