Quick answers
- Is CVE-2026-59619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59619 being exploited in the wild.
- How severe is CVE-2026-59619?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel.
- Is there a fix for CVE-2026-59619?
- 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-59619 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-59619?
- 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.
Technical details
A missing bounds check in the getCodecQp function of GC2AV1Enc.cpp allows an out-of-bounds read during quantization table lookup in AV1 video encoding. The vulnerability is triggered locally and requires system execution privileges; no user interaction is needed. An attacker with system privileges can read memory beyond the valid bounds of the quantization table.
Affected products
- Google Pixel
Timeline
- 2026-11-10: disclosed