Quick answers
- Is CVE-2026-58726 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58726 being exploited in the wild.
- How severe is CVE-2026-58726?
- 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 patch level.
- Is there a fix for CVE-2026-58726?
- A patch was published on 2026-09-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58726 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58726?
- 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
This is a privilege escalation (EoP) vulnerability caused by a missing permission check in the FsmReleaseKey function within fsm.c, a component of Google Pixel's GPCA (likely a security-related processor component). The vulnerability requires System execution privileges to trigger but enables escalation beyond that level. The attack vector is local and requires no user interaction. Google addressed this issue in the September 2026 security patch (2026-09-05 patch level) available through standard device updates.
Affected products
- Google Pixel firmware Prior to 2026-09-05 patch level
Timeline
- 2026-09-15: disclosed
- 2026-09-05: patched