CVE-2026-59606: Google Pixel firmware privilege escalation in reset register access

CVE-2026-59606 · Severity: info · Published 2026-11-10

Google Pixel device firmware contains a permissions bypass in the reset register configuration that allows non-secure software to modify global reset registers, potentially gaining system-level control. An attacker with local access to the device could exploit this to escalate privileges and take complete control of the system without requiring any user interaction.

Technologies: Google Pixel. Vendors: Google.

Quick answers

Is CVE-2026-59606 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-59606 being exploited in the wild.
How severe is CVE-2026-59606?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Pixel.
Is there a fix for CVE-2026-59606?
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-59606 attacked?
It is attacked with local access, in device firmware.
Am I affected by CVE-2026-59606?
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 permissions bypass in the sswrp_cpm.dtsi firmware component allows unprivileged (non-secure) software to modify global reset registers that should be restricted. This is a local privilege escalation vulnerability requiring code execution context on the affected device, and a patch is available in the 2026-11-05 security update.

Affected products

  • Google Pixel

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.