CVE-2026-59585: Google Pixel denial of service in SetDisplayName

CVE-2026-59585 · Severity: info · Published 2026-11-10

A missing input validation check in the SetDisplayName function of a Pixel device component can cause a denial of service, making devices unresponsive or forcing a restart. An attacker on the network can trigger this without needing to log in or interact with the user, potentially disrupting device availability.

Technologies: Google Pixel. Vendors: Google.

Quick answers

Is CVE-2026-59585 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-59585 being exploited in the wild.
How severe is CVE-2026-59585?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Pixel.
Is there a fix for CVE-2026-59585?
Yes: fixed in Pixel devices with 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-59585 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-2026-59585?
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.

How to fix

  • Fixed in: Pixel devices with security patch level 2026-11-05 or later

Technical details

A null pointer dereference vulnerability exists in the SetDisplayName function of RegInfoContact.cpp due to missing null input validation. The vulnerability is remotely exploitable without requiring elevated privileges or user interaction, allowing an attacker to crash or hang the affected component via a crafted network request.

Affected products

  • Google Pixel

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.