# CVE-2026-58788: Google Pixel out-of-bounds write in stpropnci_process_std

Source: https://junglewise.ai/threats/cve-2026-58788-in-stpropnci-process-std-of-stpropnci-std-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-58788 · Severity: info · Published 2026-11-10

An out-of-bounds write vulnerability in Google Pixel firmware's stpropnci component could allow a local attacker to escalate their privileges without needing special system permissions or user interaction. This could lead to complete device compromise and unauthorized access to sensitive data.

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

## Quick answers

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

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

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

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

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

## Technical details

A missing bounds check in the stpropnci_process_std function in stpropnci_std.cc allows local attackers to trigger an out-of-bounds write into global state, leading to privilege escalation. The vulnerability requires local access with no additional execution privileges, and no user interaction is needed for exploitation.

## Affected products

- Google Pixel firmware prior to 2026-11-05 patch level

## Timeline

- 2026-11-10: disclosed
- 2026-11-05: patched

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