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