# CVE-2026-56911: Google Pixel firmware heap buffer overflow in hwcrypto_proxy

Source: https://junglewise.ai/threats/cve-2026-56911-in-handle-fips-hmac-req-of-hwcrypto-proxy-c-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-56911 · Severity: info · Published 2026-11-10

A heap buffer overflow vulnerability exists in the cryptographic hardware proxy component of Google Pixel firmware, which could allow a local attacker with system privileges to escalate privileges or execute arbitrary code. The flaw stems from missing bounds checking when processing HMAC requests, potentially compromising the security of the entire device.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-56911?** Yes: fixed in 2026-11-05 security patch level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-56911?** 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 2026-11-05 security patch level

## Technical details

A bounds check is missing in the handle_fips_hmac_req function of hwcrypto_proxy.c, leading to a heap buffer overflow. The vulnerability requires local system execution privileges but can be exploited without user interaction. A fix is available in the 2026-11-05 security patch level.

## Affected products

- Google Pixel firmware versions prior to 2026-11-05 security 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)