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