# CVE-2026-58680: Google Pixel firmware permission bypass in cpm_mbox

Source: https://junglewise.ai/threats/cve-2026-58680-in-cpm-mbox-power-ctrl-sswrp-of-cpm-mbox-c-there-is-a-possible  
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-58680 · Severity: info · Published 2026-11-10

A permissions check failure in firmware code on Google Pixel devices allows a local attacker with system-level access to escalate privileges. An attacker who has already gained system execution privileges could exploit this to bypass additional permission restrictions, potentially gaining access to sensitive device functions or data.

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

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

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