# CVE-2026-58799: Google Pixel firmware out of bounds write in rmmi_utility

Source: https://junglewise.ai/threats/cve-2026-58799-in-multiple-functions-of-rmmi-utility-c-there-is-a-possible-way  
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-58799 · Severity: info · Published 2026-11-10

A missing bounds check in firmware code could allow an attacker to write data outside intended memory boundaries, potentially leading to remote code execution on Google Pixel devices. No authentication or user interaction is required to exploit this vulnerability, making it a direct path to complete device compromise.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel Firmware Before 2026-11-05 patch level.

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

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

## Technical details

An out-of-bounds write vulnerability exists in multiple functions of rmmi_utility.c due to missing bounds checks. The vulnerability is triggered remotely without requiring additional execution privileges. The exact attack vector and preconditions are not detailed in the advisory, but the lack of bounds validation in memory operations creates a direct path to arbitrary code execution.

## Affected products

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

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