# CVE-2026-57010: Google Pixel CHRE out-of-bounds write in data_manager

Source: https://junglewise.ai/threats/cve-2026-57010-in-encodelastscanbufferelement-of-data-manager-cc-there-is-a  
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-57010 · Severity: info · Published 2026-11-10

A logic error in the Context Hub Runtime Environment (CHRE) component of Google Pixel devices allows an attacker to write data outside the intended memory boundaries. An attacker could exploit this flaw to escalate their privileges without requiring special permissions or user interaction, potentially gaining unauthorized access to sensitive device functions.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-57010?** Yes: fixed in Android 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-57010 attacked?** It is attacked over the network or with local access, in device firmware.

**Am I affected by CVE-2026-57010?** Check whether you run Google Pixel Devices 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 Android security patch level 2026-11-05 or later

## Technical details

The vulnerability is an out-of-bounds write in the EncodeLastScanBufferElement function of data_manager.cc due to a logic error. It affects the CHRE (Context Hub Runtime Environment) component on Google Pixel devices. The flaw allows privilege escalation with no preconditions; exploitation requires no user interaction or elevated execution privileges and is reachable over the network or locally on the device.

## Affected products

- Google Pixel devices versions prior to security patch level 2026-11-05

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

- [PowerVR GPU kernel use-after-free in fence identifier handling](https://junglewise.ai/threats/cve-2026-59609-in-fence-manager-extract-iif-of-fence-manager-c-there-is-a)
- [Google Pixel Face Auth TA privilege escalation in TzPipelineInputExtractor](https://junglewise.ai/threats/cve-2026-59607-in-tzpipelineinputextractor-of-tzpipelineinputextractor-cpp-there)
- [Pixel HWCodec Firmware heap buffer overflow in encoder](https://junglewise.ai/threats/cve-2026-59594-in-spm-alloc-of-encoder-there-is-a-possible-heap-buffer-overflow)
- [Pixel devices out-of-bounds write in graphics execution](https://junglewise.ai/threats/cve-2026-58804-in-executegraphcommand-of-multiple-files-there-is-a-possible-way)
- [ARM SMMU v3 stale stream table entry information disclosure](https://junglewise.ai/threats/cve-2026-58801-in-smmu-domain-config-s1-of-arm-smmu-v3-c-there-is-a-possible-way)