Quick answers
- Is CVE-2026-55321 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55321 being exploited in the wild.
- How severe is CVE-2026-55321?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel devices.
- Is there a fix for CVE-2026-55321?
- Yes: fixed in Pixel security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55321 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-55321?
- Check whether you run Google Pixel Devices. 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: Pixel security patch level 2026-11-05 or later
Technical details
A heap buffer overflow exists in parse_prime256v1 of keymint_asn1.c due to a logic error during ASN.1 parsing of elliptic curve keys. The vulnerability is in the Secure Element KeyMint component and requires local access with execution privileges plus user interaction to exploit. Successful exploitation leads to privilege escalation on the device.
Affected products
- Google Pixel devices
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched