Quick answers
- Is CVE-2026-56909 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56909 being exploited in the wild.
- How severe is CVE-2026-56909?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Devices pre-2026-11-05 security patch level.
- Is there a fix for CVE-2026-56909?
- Yes: fixed in Pixel Update Bulletin—November 2026 (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-56909 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-56909?
- Check whether you run Google Pixel Devices 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 Update Bulletin—November 2026 (2026-11-05 security patch level or later)
Technical details
A missing permission check in the sswrp_cpm.dtsi firmware component allows non-secure software to access and modify voltage control registers, leading to local privilege escalation to system execution level. The vulnerability requires local system execution privileges to exploit and does not require user interaction. An attacker who gains initial local code execution could leverage this to escalate to higher privilege levels.
Affected products
- Google Pixel devices pre-2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed