# CVE-2026-58791: Google Pixel HWCodec firmware buffer overflow in HEVC decoder

Source: https://junglewise.ai/threats/cve-2026-58791-in-pic-timing-of-hevc-decoder-there-is-a-possible-non-heap-buffer  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-58791 · Severity: info · Published 2026-11-10

Google Pixel devices contain a buffer overflow vulnerability in the hardware video codec firmware's HEVC (H.265) decoder, specifically in picture timing handling. An attacker with access to a device and the ability to provide malicious video content could exploit this to escalate privileges and execute arbitrary code with system-level access.

Technologies: [Google Pixel HWCodec Firmware](https://junglewise.ai/threats/technologies/pixel-hwcodec-firmware). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-58791 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58791 being exploited in the wild.

**How severe is CVE-2026-58791?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel HWCodec Firmware.

**Is there a fix for CVE-2026-58791?** 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-58791 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-58791?** Check whether you run Google Pixel HWCodec Firmware. 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 non-heap buffer overflow exists in the pic_timing function of the HEVC decoder within Pixel HWCodec firmware, triggered by improper buffer boundary validation during video frame processing. Exploitation requires local access and user interaction to provide or trigger processing of malicious video content. A successful exploit grants privilege escalation to the hardware codec firmware execution context.

## Affected products

- Google Pixel HWCodec Firmware

## Timeline

- 2026-11-10: disclosed

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google HWCodec Firmware logic error in userdata_report](https://junglewise.ai/threats/cve-2026-59637-in-userdata-report-of-hwcodec-firmware-there-is-a-possible-logic)
- [Google Pixel HWCodec Firmware non-heap buffer overflow in HEVC decoder](https://junglewise.ai/threats/cve-2026-59631-in-s-inter-rps-pred-of-hevc-decoder-there-is-a-possible-non-heap)
- [Google Pixel HWCodec Firmware buffer overflow in AVC decoder](https://junglewise.ai/threats/cve-2026-59612-in-buffering-period-of-avc-decoder-there-is-a-possible-non-heap)
- [Google Pixel HWCodec Firmware buffer overflow in HEVC decoder](https://junglewise.ai/threats/cve-2026-59608-in-tone-mapping-info-of-hevc-decoder-there-is-a-possible-non-heap)
- [Google Pixel HWCodec Firmware heap buffer overflow in AV1 decoder](https://junglewise.ai/threats/cve-2026-59593-in-tile-info-of-av1-decoder-there-is-a-possible-heap-buffer)
