Quick answers
- Is CVE-2026-58698 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58698 being exploited in the wild.
- How severe is CVE-2026-58698?
- Medium severity, with a CVSS score of 6.7, published 15 September 2026.
- Which products and versions are affected?
- Google Pixel Firmware Prior to 2026-09-05 security patch level.
- Is there a fix for CVE-2026-58698?
- A patch was published on 2026-09-05: Security patch level 2026-09-05 or later addresses this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58698 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58698?
- Check whether you run Google Android or 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.
Technical details
A confused deputy vulnerability exists in the ap_pmic_poll_msg_handler function of ap_pmic_ipc.c, where improper permission validation allows a local attacker to bypass authorization checks. The vulnerability requires System execution privileges but does not require user interaction for exploitation. This is a classic confused deputy scenario where a privileged handler fails to properly validate the authority of a caller before performing a sensitive operation. The attack can lead to local privilege escalation. A fix is available in the Pixel Update Bulletin with security patch level 2026-09-05 or later.
Affected products
- Google Pixel firmware Prior to 2026-09-05 security patch level
Timeline
- 2026-09-15: disclosed
- 2026-09-05: patched: Security patch level 2026-09-05 or later addresses this issue