Quick answers
- Is CVE-2026-58680 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58680 being exploited in the wild.
- How severe is CVE-2026-58680?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Firmware Affected versions prior to 2026-11-05 security patch level.
- Is there a fix for CVE-2026-58680?
- Yes: fixed in Pixel devices updated to 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-58680 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58680?
- 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 devices updated to 2026-11-05 security patch level or later
Technical details
The vulnerability is a permission bypass due to a precondition check failure in the cpm_mbox_power_ctrl_sswrp function of cpm_mbox.c. It requires local access with system execution privileges and can lead to privilege escalation. This is a privilege escalation vulnerability affecting the ACFW (Application Coprocessor Firmware) component on Pixel devices.
Affected products
- Google Pixel firmware Affected versions prior to 2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched