# CVE-2026-59601: Google Pixel firmware heap buffer overflow in CLDMA audio processing

Source: https://junglewise.ai/threats/cve-2026-59601-in-calculatesamplerate-of-cldma-alcedo-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-59601 · Severity: info · Published 2026-11-10

A heap buffer overflow vulnerability exists in audio processing firmware on Google Pixel devices, allowing an attacker without elevated privileges to remotely disclose sensitive device information. The vulnerability requires no user interaction and could expose confidential data stored in device memory.

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

## Quick answers

**Is CVE-2026-59601 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59601 being exploited in the wild.

**How severe is CVE-2026-59601?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel Firmware earlier than 2026-11-05 patch level.

**Is there a fix for CVE-2026-59601?** Yes: fixed in Pixel 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-59601 attacked?** It is attacked over the network, in device firmware.

**Am I affected by CVE-2026-59601?** Check whether you run 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.

## How to fix

- Fixed in Pixel security patch level 2026-11-05 or later

## Technical details

A logic error in the CalculateSampleRate function of cldma_alcedo.cc permits heap buffer overflow, enabling information disclosure via remote network access. The vulnerability affects Pixel firmware components and is fixed in the November 2026 security patch level (2026-11-05 or later).

## Affected products

- Google Pixel firmware earlier than 2026-11-05 patch level

## 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 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 out of bounds read/write in log formatting](https://junglewise.ai/threats/cve-2026-59574-in-notifypollingloopframes-of-hal-fwlog-cc-there-is-a-possible)
- [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)