# CVE-2026-56989: Google Pixel out-of-bounds write privilege escalation

Source: https://junglewise.ai/threats/cve-2026-56989-google-pixel-out-of-bounds-write-privilege-escalation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-56989 · Severity: medium · CVSS 6.7 · Published 2026-09-15

Google Pixel devices contain a missing bounds check in kernel components that allows an attacker with local system access to write data outside allocated memory regions. This vulnerability can lead to privilege escalation, enabling an attacker to gain complete control over the affected device with system-level permissions.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android), [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

**How severe is CVE-2026-56989?** Medium severity, with a CVSS score of 6.7, published 15 September 2026.

**Which products and versions are affected?** Google Pixel Devices Before 2026-09-05 patch level.

**Is there a fix for CVE-2026-56989?** A patch was published on 2026-09-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-56989 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-56989?** Check whether you run Google Android or Google Pixel Devices 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.

## Technical details

CVE-2026-56989 is an out-of-bounds write vulnerability caused by missing bounds checking in multiple kernel locations on Google Pixel devices. The vulnerability requires local access with system execution privileges to exploit; user interaction is not required. An attacker can leverage this flaw to corrupt memory and escalate privileges to system level. The vulnerability is addressed in the Pixel security patch level 2026-09-05 or later, released September 15, 2026.

## Affected products

- Google Pixel devices Before 2026-09-05 patch level

## Timeline

- 2026-09-15: disclosed
- 2026-09-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)