Quick answers
- Is CVE-2026-59625 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59625 being exploited in the wild.
- How severe is CVE-2026-59625?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel prior to 2026-11-05 patch level.
- Is there a fix for CVE-2026-59625?
- 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-59625 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-59625?
- 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
An out-of-bounds write vulnerability exists in GetTwiddledMiptreeSparsePageMap of texmgmt.c in the PowerVR-GPU driver. The vulnerability stems from a logic error in memory bounds checking and can be triggered remotely without additional execution privileges. Successful exploitation results in remote code execution on the affected Pixel device.
Affected products
- Google Pixel prior to 2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched