# CVE-2026-58690: Google Pixel trusted execution environment out-of-bounds write

Source: https://junglewise.ai/threats/cve-2026-58690-in-multiple-functions-of-bitmap-image-buffer-h-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-58690 · Severity: info · Published 2026-11-10

A flaw in Google Pixel firmware's image processing code can cause an out-of-bounds memory write in the trusted execution environment (the isolated security processor that protects sensitive data) due to an integer overflow. An attacker with local access can exploit this to escalate privileges without needing special permissions, potentially gaining full control of sensitive security functions on the device.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel Firmware All versions before 2026-11-05 security patch.

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

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

## Technical details

An integer overflow in multiple functions of bitmap_image_buffer.h allows an out-of-bounds write to the trusted execution environment heap. The vulnerability requires local access but no additional execution privileges, and can lead to local escalation of privilege. The affected firmware component processes bitmap image data where insufficient bounds validation during size calculations permits memory corruption.

## Affected products

- Google Pixel firmware All versions before 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 firmware heap buffer overflow in CLDMA audio processing](https://junglewise.ai/threats/cve-2026-59601-in-calculatesamplerate-of-cldma-alcedo-cc-there-is-a-possible)
- [Google Pixel firmware out-of-bounds write in NCI command handler](https://junglewise.ai/threats/cve-2026-59587-in-stpropnci-prop-st-build-set-custom-polling-cmd-of-stpropnci)
- [Google Pixel firmware out of bounds read/write in log formatting](https://junglewise.ai/threats/cve-2026-59574-in-notifypollingloopframes-of-hal-fwlog-cc-there-is-a-possible)
- [Google Pixel firmware information disclosure on warm reset](https://junglewise.ai/threats/cve-2026-58808-in-multiple-locations-there-is-a-possible-way-to-dump-secure)
- [Google Pixel firmware memory bounds check in secure boot](https://junglewise.ai/threats/cve-2026-58805-in-multiple-locations-there-is-a-possible-way-to-zero-arbitrary)