Quick answers
- Is CVE-2026-59624 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59624 being exploited in the wild.
- How severe is CVE-2026-59624?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Devices with security patch level earlier than 2026-11-05.
- Is there a fix for CVE-2026-59624?
- Yes: fixed in Security patch level 2026-11-05 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59624 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59624?
- 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: Security patch level 2026-11-05 and later
Technical details
An out-of-bounds read vulnerability exists in video decoder firmware on Google Pixel devices due to a logic error that allows direct memory access beyond allocated buffers. The vulnerability can be triggered locally and leads to information disclosure; no additional execution privileges are required and user interaction is not needed for exploitation.
Affected products
- Google Pixel Devices with security patch level earlier than 2026-11-05
Timeline
- 2026-11-10: disclosed