Quick answers
- Is CVE-2026-58805 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58805 being exploited in the wild.
- How severe is CVE-2026-58805?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel firmware.
- Is there a fix for CVE-2026-58805?
- Yes: fixed in Pixel devices receiving 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-58805 attacked?
- It is attacked with physical access, in device firmware.
- Am I affected by CVE-2026-58805?
- Check whether you run Google Pixel Firmware. 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 devices receiving security patch level 2026-11-05 or later
Technical details
The vulnerability exists in secure boot firmware processing where image body addresses are not properly validated before being used to zero memory regions. This missing bounds check allows an attacker to write zeros to arbitrary secure memory locations. Exploitation requires physical access to the device (local attack vector) and no user interaction.
Affected products
- Google Pixel firmware
Timeline
- 2026-11-10: disclosed