Skip to main content
All incident reports
Incident report

Pwn2Own teams demonstrate remote Pixel 10 exploits on fully patched phones

Three research teams demonstrated remote exploits against fully patched Google Pixel 10 phones at Pwn2Own Ireland on 8 October and were paid a combined $562,500. The bugs were passed to the vendors, and the contest organiser has published no technical detail and no fix.

· First published

The short version

  • The contest. Three teams broke into Google Pixel 10 handsets at Pwn2Own Ireland on 8 October, at an event whose rules require every target to run fully patched software. Ikotas Labs took the top prize of $300,000.
  • Known bugs in the chain. At least two of the three Pixel entries used a bug that was already known before the attempt; the organiser calls such an entry a collision, which can still be accepted at a lower prize. One entry chained a collision with a zero-day, a flaw unknown to the vendor when it was used.
  • Disclosure terms. Winning teams hand their exploits and write-ups to Trend Micro's Zero Day Initiative, which passes the flaws to the affected vendors and gives them 90 days to patch before publishing technical details.
  • Other targets. Samsung's Galaxy S26 was exploited in all seven attempts, and printers, smart home hubs, AI tools and a blood pressure monitor were also broken. No team attempted the iPhone 17 or WhatsApp.

Timeline

DateEvent
SeptemberGoogle patches a Pixel modem flaw, CVE-2026-58704, which it says may have been under limited, targeted exploitation.
6 OctGoogle publishes its October Pixel bulletin, which does not mention the contest.
8 OctThree teams demonstrate remote exploits against fully patched Pixel 10 phones at Pwn2Own Ireland in Cork.
9 OctZDI has posted the results but not published how the exploits work; its list shows no fix and no step for Pixel owners.

The Pixel 10 wins

Three teams demonstrated remote break-ins of the Pixel 10 on 8 October at Pwn2Own Ireland in Cork. All three entries were registered as remote exploits, which under the rules means entry through web content opened in the phone's default browser or over one of four radio links: NFC, Wi-Fi, Bluetooth or baseband. A winning entry had to run attacker-chosen code on the phone or pull sensitive data from it. ZDI has not published which route each team used or what each exploit did on the device.

Ikotas Labs earned the full $300,000 and 30 points for chaining several issues, and ZDI named it Master of Pwn with four wins totalling $361,000 and 42.5 points. Xint, the team of Tim Becker and Yves Bieri, received $150,000 and 15 points for an entry built on a single bug collision. A third team including Dimitrios Valsamaras and Ken Gannon received $112,500 and 22.5 points for a chain of one known bug and one zero-day. The three Pixel wins paid $562,500 in total.

What happens to the bugs

Contest rules require every target to be fully patched. An entry that relies on a bug already known to the vendor or the organiser — which ZDI calls a collision — can still be accepted at a lower prize. Winning teams hand their exploits and write-ups to ZDI, the Zero Day Initiative run by Trend Micro, which passes the bugs to the affected vendors. According to a June article from TrendAI, Trend Micro's enterprise security business, vendors then have 90 days to release patches before ZDI publishes full technical details.

Google published its October Pixel bulletin on 6 October, two days before the demonstrations, and it does not mention the contest. ZDI's results list no fix and no step for Pixel owners to take. SecurityWeek reports that affected vendors will be provided with the full details of all exploits.

Other targets and a separate Pixel flaw

Samsung's Galaxy S26 was exploited in all seven attempts on it, and six of the seven winning entries included at least one collision. ZDI said one bug in the Galaxy S26 chain Ikotas Labs used was already known to the vendor but unpatched at the time. Ikotas also broke OpenAI's Codex coding agent and Oracle's Autonomous AI Database. A Sonos Era 300 hack paid $50,000, and rewards of $40,000 went to exploits against Oracle's database, Codex, Nvidia's Dynamo inference framework, the LiteLLM gateway and the Philips Hue Bridge Pro.

Across the contest, 51 of 63 scheduled attempts succeeded and awards came to more than $1.2 million. No team attempted Apple's iPhone 17 or WhatsApp, each carrying a $300,000 top prize. Separately, Google said in September that a Pixel modem flaw, CVE-2026-58704, may have been under limited, targeted exploitation; phones at patch level 2026-09-05 or later have that fix. No source connects that flaw to the contest.

What is not known yet

  • How each of the three Pixel 10 exploits works, which route it used and what it did on the device; ZDI had not published this as of 9 October.
  • Whether Google has fixed the contest bugs, and when any patches will reach devices.
  • What the collision label on the Ikotas Labs entry means, and why it still received the full prize.
  • Whether any of the demonstrated flaws are being exploited outside the contest.
  • Whether the September Pixel modem flaw and the contest bugs are related; no source links them.

What to do

If you manage Pixel phones

  1. Check the device patch level: phones at 2026-09-05 or later carry the September modem fix for CVE-2026-58704.
  2. Apply Google's monthly Pixel updates and watch the bulletin for fixes arising from the contest.
  3. Treat content in the default browser and the NFC, Wi-Fi, Bluetooth and baseband links as the routes the contest exploits used.

If you run the other targeted products

  1. Track vendor advisories for the Samsung Galaxy S26, LiteLLM, Oracle Autonomous AI Database, Nvidia Dynamo, OpenAI Codex, and the printers and smart home hubs demonstrated.
  2. Expect technical details within 90 days of 8 October and book patching windows before that.

For everyone else

  1. Treat contest results as advance notice that current, fully patched products can be broken remotely; patched does not mean unexploitable.
  2. Set and enforce a patch cadence for mobile devices and any endpoint reachable from the internet or over radio links.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.