Quick answers
- Is CVE-2026-59630 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59630 being exploited in the wild.
- How severe is CVE-2026-59630?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Before 2026-11-05 security patch level.
- Is there a fix for CVE-2026-59630?
- Yes: fixed in Pixel devices with 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-59630 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59630?
- 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 security patch level 2026-11-05 or later
Technical details
A logic error in the check_constraint_monotonicity function of the Trusty TZ kernel allows downgrade of stored security policies and rollback protection bypass. The vulnerability requires local access but no additional execution privileges. An attacker can exploit this to achieve privilege escalation within the trusted execution environment.
Affected products
- Google Pixel Before 2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched