# CVE-2026-95404: Google Pixel coprocessor memory privilege escalation

Source: https://junglewise.ai/threats/cve-2026-95404-in-multiple-locations-there-is-a-possible-way-to-modify  
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-95404 · Severity: info · Published 2026-11-10

Google Pixel devices contain a security flaw in coprocessor firmware that allows non-privileged software to modify memory and gain elevated system access. An attacker with code execution at a lower privilege level can exploit this to escalate to full system privileges without requiring any user interaction. This could allow malicious apps or compromised software to take complete control of a device.

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

## Quick answers

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

**How severe is CVE-2026-95404?** 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-95404?** Yes: fixed in Google Pixel devices with 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-95404 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-95404?** 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 Google Pixel devices with 2026-11-05 security patch level or later

## Technical details

The vulnerability stems from insecure default values in coprocessor firmware that fail to properly protect instruction and data memory regions from non-secure software access. An attacker with local code execution can write to coprocessor memory to escalate privileges to System level. The flaw requires no user interaction and is fixed by applying the November 2026-11-05 security patch level.

## Affected products

- Google Pixel Before 2026-11-05 security patch level

## 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 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)
- [Google Pixel denial of service via anti-rollback fuse logic error](https://junglewise.ai/threats/cve-2026-59636-in-has-booted-successfully-of-sys-state-setup-otp-ta-c-there-is-a)