Quick answers
- Is CVE-2026-59608 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59608 being exploited in the wild.
- How severe is CVE-2026-59608?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel HWCodec Firmware prior to 2026-11-05 security patch level.
- Is there a fix for CVE-2026-59608?
- Yes: fixed in Pixel Update Bulletin 2026-11-05 or later security patch level. Until then: Apply the November 2026 Pixel security update to patch level 2026-11-05 or later. Avoid opening untrusted video files until the patch is applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59608 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59608?
- Check whether you run Google Pixel HWCodec Firmware 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 Update Bulletin 2026-11-05 or later security patch level
Apply the November 2026 Pixel security update to patch level 2026-11-05 or later. Avoid opening untrusted video files until the patch is applied.
Technical details
A non-heap buffer overflow exists in the tone_mapping_info function of the HEVC decoder within Google's HWCodec firmware, triggered by improper buffer bounds checking during video frame processing. The vulnerability requires local execution context and user interaction (such as playing a malicious video file) to trigger. Successful exploitation leads to privilege escalation with code execution in the firmware security context.
Affected products
- Google Pixel HWCodec Firmware prior to 2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched