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