Quick answers
- Is CVE-2026-95401 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95401 being exploited in the wild.
- How severe is CVE-2026-95401?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel all supported Pixel devices prior to 2026-11-05 patch level.
- Is there a fix for CVE-2026-95401?
- Yes: fixed in Pixel Update Bulletin 2026-11-05 or later. Until then: Apply the November 2026 security patch (2026-11-05 or later) to your Pixel device. Check your device's security patch level in Settings and accept the update when available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95401 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-95401?
- Check whether you run Google Pixel 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: Pixel Update Bulletin 2026-11-05 or later
Apply the November 2026 security patch (2026-11-05 or later) to your Pixel device. Check your device's security patch level in Settings and accept the update when available.
Technical details
The vulnerability is a non-heap buffer overflow in the knee_function_info function of hevc_decoder that allows local privilege escalation. The attack requires user interaction (likely loading a malicious video file) and local execution privileges to exploit. A fix is available in the November 2026 security patch.
Affected products
- Google Pixel all supported Pixel devices prior to 2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched