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