Quick answers
- Is CVE-2026-59636 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59636 being exploited in the wild.
- How severe is CVE-2026-59636?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel.
- Is there a fix for CVE-2026-59636?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59636 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59636?
- Check whether you run Google Pixel. 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.
Technical details
A logic error in sys_state_setup_otp_ta.c's has_booted_successfully function allows premature anti-rollback fuse updates. The vulnerability resides in the bootloader/OTP (one-time programmable) management component and can be exploited locally without requiring elevated privileges. Successful exploitation results in permanent DoS by corrupting OTP fuse state needed for secure boot verification.
Affected products
- Google Pixel
Timeline
- 2026-11-10: advisory