# CVE-2026-59613: Google Pixel out-of-bounds read in input validation

Source: https://junglewise.ai/threats/cve-2026-59613-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-59613 · Severity: info · Published 2026-11-10

Google Pixel devices contain improper input validation that could allow an attacker to trigger an out-of-bounds memory read remotely, causing temporary denial of service. No user interaction or elevated privileges are required to exploit this vulnerability, making it accessible to an attacker on the network.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-59613?** Yes: fixed in Pixel 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-59613 attacked?** It is attacked over the network, in device firmware.

**Am I affected by CVE-2026-59613?** 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 security patch level 2026-11-05 or later

## Technical details

An out-of-bounds read vulnerability exists due to insufficient input validation in multiple code locations within Google Pixel device firmware and kernel components. The vulnerability can be triggered remotely without authentication or user interaction, resulting in denial of service through a temporary device hang or crash. No code execution is possible via this vector.

## Affected products

- Google Pixel prior to 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 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)