# CVE-2026-58804: Pixel devices out-of-bounds write in graphics execution

Source: https://junglewise.ai/threats/cve-2026-58804-in-executegraphcommand-of-multiple-files-there-is-a-possible-way  
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-58804 · Severity: info · Published 2026-11-10

A flaw in the graphics command execution code on Pixel devices allows an attacker to write data outside allocated memory boundaries through an oversized scratch memory declaration. This could be exploited locally to gain elevated system privileges without requiring special permissions or user interaction, potentially compromising sensitive device data and functionality.

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

## Quick answers

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

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

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

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

**Am I affected by CVE-2026-58804?** 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 Security patch level 2026-11-05 or later

## Technical details

An incorrect bounds check in ExecuteGraphCommand fails to validate scratch memory allocation size, allowing a local attacker to trigger an out-of-bounds write. The vulnerability affects multiple firmware and driver components across Pixel devices and can be exploited without elevated privileges. The issue is addressed by fixes applied to graphics-related firmware and kernel components in the November 2026 security patch level.

## Affected products

- Google Pixel devices Devices with security patch level prior to 2026-11-05

## 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)
- [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)
- [Google Pixel hwmgr elevation of privilege via uninitialized data](https://junglewise.ai/threats/cve-2026-58785-in-update-user-consent-of-main-rs-there-is-a-possible-elevation)