# CVE-2026-59587: Google Pixel firmware out-of-bounds write in NCI command handler

Source: https://junglewise.ai/threats/cve-2026-59587-in-stpropnci-prop-st-build-set-custom-polling-cmd-of-stpropnci  
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-59587 · Severity: info · Published 2026-11-10

A firmware component in Google Pixel devices that handles NFC communication commands contains a missing bounds check, allowing an attacker to write data beyond allocated memory boundaries. This vulnerability enables local privilege escalation without requiring special user permissions or interaction, potentially giving an attacker full control over the device.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel firmware.

**Is there a fix for CVE-2026-59587?** 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-59587 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-59587?** 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 security patch level 2026-11-05 or later

## Technical details

A missing bounds check in stpropnci_prop_st_build_set_custom_polling_cmd function in stpropnci_prop_st.cc permits an out-of-bounds write to global memory. The vulnerability is exploitable locally without additional execution privileges or user interaction, leading to memory corruption and privilege escalation in the NCI (NFC Controller Interface) firmware subsystem.

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