Quick answers
- Is CVE-2026-59574 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59574 being exploited in the wild.
- How severe is CVE-2026-59574?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel firmware.
- Is there a fix for CVE-2026-59574?
- Yes: fixed in Pixel devices with security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59574 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59574?
- Check whether you run Google Pixel Firmware. 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 with security patch level 2026-11-05 or later
Technical details
An incorrect bounds check in the notifyPollingLoopFrames function of hal_fwlog.cc in Google Pixel firmware allows an out-of-bounds read and write when formatting firmware log notifications. The vulnerability is reachable without special privileges and does not require user interaction. The primary impact is information disclosure through physical memory leakage.
Affected products
- Google Pixel firmware
Timeline
- 2026-11-10: disclosed