Quick answers
- Is CVE-2026-59575 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59575 being exploited in the wild.
- How severe is CVE-2026-59575?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel.
- Is there a fix for CVE-2026-59575?
- 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-59575 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59575?
- Check whether you run Google Pixel. 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
An out of bounds write vulnerability exists in stpropnci_cb_observe_mode_suspend of stpropnci_prop_android.cc due to missing bounds checking. A local attacker can trigger this condition to corrupt global state in the NCI firmware component, leading to denial of service. The vulnerability requires no additional execution privileges.
Affected products
- Google Pixel
Timeline
- 2026-11-10: disclosed