# CVE-2026-56960: Google Pixel use-after-free in kernel

Source: https://junglewise.ai/threats/cve-2026-56960-google-pixel-use-after-free-in-kernel  
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-56960 · Severity: critical · CVSS 9.8 · Published 2026-09-15

A use-after-free vulnerability in Google Pixel device firmware allows a local attacker to escalate privileges and gain complete control of the device without requiring user interaction or special permissions. This vulnerability could enable theft of sensitive data, installation of malware, or unauthorized access to corporate or personal information stored on the device.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

**How severe is CVE-2026-56960?** Critical severity, with a CVSS score of 9.8, published 15 September 2026.

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

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

**How is CVE-2026-56960 attacked?** It is attacked over the network.

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

A use-after-free vulnerability due to a logic error exists in multiple locations within the Pixel kernel and firmware components. The vulnerability is reachable via a network vector and requires no additional execution privileges or user interaction for exploitation. An attacker can exploit this to achieve remote escalation of privilege (EoP) and potentially remote code execution (RCE) depending on the affected subcomponent. Patches were made available as part of the 2026-09-05 security patch level for all supported Pixel devices.

## Affected products

- Google Pixel 2026-09-05 patch level and earlier

## Timeline

- 2026-09-15: disclosed: Published in Google Pixel Update Bulletin—September 2026
- 2026-09-05: patched: Patch level 2026-09-05 addresses this issue

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