Quick answers
- Is CVE-2026-0175 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0175 being exploited in the wild.
- How severe is CVE-2026-0175?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel devices.
- Is there a fix for CVE-2026-0175?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-0175 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-0175?
- 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.
Technical details
A logic error in the wrapped key import process allows bypass of key authorization policies, enabling local privilege escalation. The vulnerability is present in multiple locations within the KeyMint or related cryptographic key management components on Pixel devices. Exploitation requires local access but no additional privileges or user interaction.
Affected products
- Google Pixel devices
Timeline
- 2026-11-10: disclosed
- 2026-11-10: advisory: Pixel Update Bulletin for November 2026