# CVE-2026-55317: Google Pixel Bootloader out-of-bounds write in printf

Source: https://junglewise.ai/threats/cve-2026-55317-google-pixel-bootloader-out-of-bounds-write-in-printf  
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-55317 · Severity: medium · CVSS 6.7 · Published 2026-09-15

A vulnerability in the bootloader's printf function could allow a local attacker with system-level privileges to write data outside memory boundaries, potentially leading to privilege escalation. This affects Google Pixel devices and could undermine the security protections of the bootloader, the firmware component responsible for safely starting the device.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel Bootloader.

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

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

An out-of-bounds write vulnerability exists in the printf.c implementation within the bootloader due to improper input validation. The vulnerability is triggered when printf processes specially crafted format strings or input, allowing an attacker to write beyond allocated buffer boundaries. Exploitation requires System execution privileges on the local system and does not require user interaction. A successful exploit could lead to elevation of privilege within the bootloader environment. The issue was patched in the September 2026 security update (patch level 2026-09-05) for all supported Pixel devices.

## Affected products

- Google Pixel Bootloader

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