Quick answers
- Is CVE-2026-59598 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59598 being exploited in the wild.
- How severe is CVE-2026-59598?
- 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-59598?
- Yes: fixed in Pixel devices with 2026-11-05 security patch level or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59598 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59598?
- 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 security patch level or later
Technical details
A use-after-free vulnerability exists in the platform_rio_ncp_wdt_handler function of edgetpu_rio.c in the EdgeTPU Driver. The vulnerability requires local access and user interaction to exploit, allowing an attacker to escalate privileges to execute arbitrary code on the device. The fixed patch level is 2026-11-05.
Affected products
- Google Pixel prior to 2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched