# CVE-2026-55365: Google Pixel Bootloader out-of-bounds write in remap.c

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

A firmware component in Google Pixel devices contains an out-of-bounds memory write flaw in code that maps memory regions during boot. An attacker with local system-level access can exploit this to escalate privileges and gain complete control of the device, potentially leading to unauthorized access to all device data and functions.

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-55365 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55365 being exploited in the wild.

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

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

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

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

The vulnerability is an out-of-bounds write in multiple functions of remap.c due to an incorrect bounds check in the Bootloader component. The flaw allows an attacker with System execution privileges to write beyond allocated memory boundaries, leading to privilege escalation. This is a local vulnerability requiring system-level access; it does not require user interaction. Google patched this issue in the Pixel security update with patch level 2026-09-05 or later.

## Affected products

- Google Pixel Bootloader pre-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)