# CVE-2026-58785: Google Pixel hwmgr elevation of privilege via uninitialized data

Source: https://junglewise.ai/threats/cve-2026-58785-in-update-user-consent-of-main-rs-there-is-a-possible-elevation  
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-58785 · Severity: info · Published 2026-11-10

Google Pixel devices contain a vulnerability in the hardware manager component that allows a local attacker with system-level privileges to escalate their access further through uninitialized data in the user consent update function. An attacker with initial system access could gain additional privileges, potentially leading to complete device compromise and access to sensitive user data.

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

## Quick answers

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

**How severe is CVE-2026-58785?** 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-58785?** A patch was published on 2026-11-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58785 attacked?** It is attacked with local access, in device firmware.

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

The vulnerability exists in the update_user_consent function of hwmgr (main.rs) and stems from use of uninitialized data, enabling privilege escalation. The attack requires local access and system execution privileges but does not require user interaction. An attacker with these preconditions can escalate their privileges further within the system.

## Affected products

- Google Pixel devices prior to 2026-11-05 security 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)