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