Quick answers
- Is CVE-2026-58757 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58757 being exploited in the wild.
- How severe is CVE-2026-58757?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Devices Prior to 2026-11-05 security patch level.
- Is there a fix for CVE-2026-58757?
- 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-58757 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58757?
- Check whether you run Google Pixel Devices 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.
Technical details
An out-of-bounds write vulnerability exists in mfc_alloc_enc_roi_buffer() in mfc_buf.c due to improper heap buffer size validation. This allows a local attacker to overflow the heap buffer and corrupt adjacent memory, leading to privilege escalation. No special privileges or user interaction are required for exploitation.
Affected products
- Google Pixel devices Prior to 2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed