# CVE-2026-95403: Google Pixel shared memory bitmap out-of-bounds write

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

An out-of-bounds memory write vulnerability exists in the shared memory tracking bitmap on Google Pixel devices due to missing bounds checking. A local attacker with minimal privileges can exploit this flaw to escalate their access to higher privilege levels, potentially gaining control over sensitive device functions.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel.

**Is there a fix for CVE-2026-95403?** 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-95403 attacked?** It is attacked with local access, in device firmware.

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

This is a missing bounds check vulnerability in the shared memory tracking bitmap that permits out-of-bounds write operations. The vulnerability requires local code execution but no additional privileges. Exploitation leads to local privilege escalation via memory corruption.

## Affected products

- Google Pixel

## Timeline

- 2026-11-10: disclosed

## 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 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)