# CVE-2026-59596: Google Pixel security coprocessor code execution via insecure default

Source: https://junglewise.ai/threats/cve-2026-59596-in-multiple-functions-of-mpu-c-there-is-a-possible-way-to-execute  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

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

A security coprocessor on Google Pixel devices can be tricked into executing untrusted code from non-secure memory due to an insecure default configuration in the memory protection unit. An attacker with local access can escalate privileges and compromise the device's security features without needing special permissions or user interaction.

Technologies: [Google Pixel](https://junglewise.ai/threats/technologies/google-pixel). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-59596 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59596 being exploited in the wild.

**How severe is CVE-2026-59596?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel Unpatched Pixel devices prior to 2026-11-05 security patch.

**Is there a fix for CVE-2026-59596?** A patch was published on 2026-11-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-59596 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-59596?** 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.

## Technical details

The vulnerability exists in multiple functions of mpu.c (memory protection unit code) in the Pixel firmware, where an insecure default value allows code execution from non-secure memory regions in the security coprocessor. This represents a privilege escalation (EoP) flaw that can be exploited locally without additional execution privileges. The issue affects the Trusty firmware component and was patched in the November 2026 Pixel security update.

## Affected products

- Google Pixel Unpatched Pixel devices prior to 2026-11-05 security patch

## Timeline

- 2026-11-10: disclosed
- 2026-11-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google Pixel coprocessor memory privilege escalation](https://junglewise.ai/threats/cve-2026-95404-in-multiple-locations-there-is-a-possible-way-to-modify)
- [Google Pixel shared memory bitmap out-of-bounds write](https://junglewise.ai/threats/cve-2026-95403-in-multiple-locations-there-is-a-possible-way-to-trigger-an-out)
- [Google Pixel HWCodec buffer overflow in HEVC decoder](https://junglewise.ai/threats/cve-2026-95402-in-slice-header-of-hevc-decoder-there-is-a-possible-non-heap)
- [Google Pixel hevc_decoder buffer overflow](https://junglewise.ai/threats/cve-2026-95401-in-knee-function-info-of-hevc-decoder-there-is-a-possible-non)
- [Google Pixel FaceAuth race condition in biometric enrollment](https://junglewise.ai/threats/cve-2026-95399-in-multiple-functions-of-face-status-h-there-is-a-possible-way-to)