# CVE-2026-59574: Google Pixel firmware out of bounds read/write in log formatting

Source: https://junglewise.ai/threats/cve-2026-59574-in-notifypollingloopframes-of-hal-fwlog-cc-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-59574 · Severity: info · Published 2026-11-10

A vulnerability in Google Pixel device firmware log formatting code allows an attacker to read and write memory outside safe boundaries due to an incorrect bounds check. This could expose sensitive device information and potentially allow unauthorized modification of firmware operations without requiring additional privileges or user interaction.

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

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

## 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 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)
- [Google Pixel firmware out of bounds write in rmmi_utility](https://junglewise.ai/threats/cve-2026-58799-in-multiple-functions-of-rmmi-utility-c-there-is-a-possible-way)