CVE-2026-59614: Google Pixel secure cache line disclosure on warm reset

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

A vulnerability in Google Pixel device firmware allows sensitive data stored in secure processor cache to be dumped into non-secure memory when the device undergoes a warm reset. An attacker with system-level access can exploit this missing permission check to read secure information that should remain protected, such as cryptographic keys or authentication data.

Technologies: Google Pixel. Vendors: Google.

Quick answers

Is CVE-2026-59614 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-59614 being exploited in the wild.
How severe is CVE-2026-59614?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Pixel.
Is there a fix for CVE-2026-59614?
Yes: fixed in Pixel devices updated to 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-59614 attacked?
It is attacked with local access.
Am I affected by CVE-2026-59614?
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.

How to fix

  • Fixed in: Pixel devices updated to 2026-11-05 security patch level or later

Technical details

The vulnerability exists in multiple functions of oem_svc_setup.c due to missing permission checks that should prevent secure cache lines from being accessible during warm reset transitions. An attacker with system execution privileges can trigger the disclosure of secure cache contents into non-secure memory. No user interaction is required for exploitation.

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.