Quick answers
- Is CVE-2026-95402 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95402 being exploited in the wild.
- How severe is CVE-2026-95402?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel.
- Is there a fix for CVE-2026-95402?
- Yes: fixed in Pixel devices with 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-95402 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-95402?
- Check whether you run Google Pixel. 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 devices with security patch level 2026-11-05 or later
Technical details
A non-heap buffer overflow occurs in the slice_header function of the HEVC decoder that processes video frames. The vulnerability allows local code execution with the privileges of the hardware codec component. The attack requires user interaction to process a malicious video file, but no authentication or network access is needed beyond local playback.
Affected products
- Google Pixel
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched