# CVE-2026-58681: Google Pixel MFC integer overflow out-of-bounds write

Source: https://junglewise.ai/threats/cve-2026-58681-in-multiple-locations-there-is-a-possible-out-of-bounds-write-due  
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-58681 · Severity: info · Published 2026-11-10

An integer overflow vulnerability in the Media Format Codec (MFC) component of Google Pixel devices can lead to out-of-bounds memory writes and remote code execution. An attacker can exploit this remotely without user interaction or special privileges, potentially gaining complete control of the device.

Technologies: [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel Devices All supported versions prior to 2026-11-05 patch level.

**Is there a fix for CVE-2026-58681?** Yes: fixed in 2026-11-05 security patch level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58681 attacked?** It is attacked over the network, in device firmware.

**Am I affected by CVE-2026-58681?** 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.

## How to fix

- Fixed in 2026-11-05 security patch level

## Technical details

The vulnerability is an integer overflow in the MFC kernel component leading to out-of-bounds write, classified as RCE with high severity. It affects Google Pixel devices and is exploitable remotely with no authentication or user interaction required. A patch is available in the 2026-11-05 security patch level for all supported Pixel devices.

## Affected products

- Google Pixel devices All supported versions prior to 2026-11-05 patch level

## Timeline

- 2026-11-10: disclosed
- 2026-11-05: patched

## 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

- [PowerVR GPU kernel use-after-free in fence identifier handling](https://junglewise.ai/threats/cve-2026-59609-in-fence-manager-extract-iif-of-fence-manager-c-there-is-a)
- [Google Pixel Face Auth TA privilege escalation in TzPipelineInputExtractor](https://junglewise.ai/threats/cve-2026-59607-in-tzpipelineinputextractor-of-tzpipelineinputextractor-cpp-there)
- [Pixel HWCodec Firmware heap buffer overflow in encoder](https://junglewise.ai/threats/cve-2026-59594-in-spm-alloc-of-encoder-there-is-a-possible-heap-buffer-overflow)
- [Pixel devices out-of-bounds write in graphics execution](https://junglewise.ai/threats/cve-2026-58804-in-executegraphcommand-of-multiple-files-there-is-a-possible-way)
- [ARM SMMU v3 stale stream table entry information disclosure](https://junglewise.ai/threats/cve-2026-58801-in-smmu-domain-config-s1-of-arm-smmu-v3-c-there-is-a-possible-way)