OpenAI: 948 Linux paths to root for $1.2 million

OpenAI said on November 4, 2026 that a research pipeline built around an upcoming cyber model proved 948 distinct ways for an ordinary local user to become root on Linux. The mid-October run cost $1,213,430 in API credits, about $1,279 for each of those local privilege escalations. The company says the virtual machines were a stock desktop distribution, with the usual kernel protections left on, under the same kind of rules used at public hacking contests.

The funnel behind the headline is the part operators should remember. OpenAI says the system analyzed 2,308 candidate kernel findings, reproduced 1,724 of them, and also produced proofs for 291 information leaks. The 948 figure is the count of distinct issues after variant analysis and candidate patches, drawn from a larger set of working local root demonstrations. Human researchers reviewed the output before reports went to maintainers. This briefing stops at those counts. It does not describe how any of the bugs were triggered.

The patches are not one update

OpenAI says it followed Linux kernel guidance and sent hundreds of reports and patches for the critical cases first. The rest are going out gradually with partners in its Patch the Planet effort. A blog post is not a distribution advisory. A host is exposed until the kernel package from its own vendor includes the fix and the machine has rebooted into it.

The same note says that while the scan was running, other contributors patched or staged fixes for more than 100 Linux local root bugs inside ten days, with about 300 more already in public discussion. The discovery rate is the story. In June, under the same initiative, OpenAI said GPT-5.5 Cyber had produced 24 local root demonstrations. The October run is the scaled version of that work.

OpenAI compared the $1.2 million spend with historical contest awards of $20,000 and $70,000 for a Linux kernel local root bug. On that arithmetic the 948 findings would sit in a hypothetical band of about $18.9 million to $66.3 million. That is a benchmark the company published, not a price list and not a claim that every finding has a bounty.

What to do while the fixes land

Apply current kernel updates on servers, desktops, CI runners, and developer VMs, then reboot. Track which of the reported issues your distribution has actually shipped. A machine that “was patched last quarter” can still be inside this set.

OpenAI’s warning to operators is the useful line. On a system that has missed current patches, plan for a well-resourced attacker who already has an ordinary user account as someone who can reach root. Remove local accounts that no longer match a job. Keep untrusted code in a sandbox or a microVM. OpenAI names Firecracker and gVisor as examples of that isolation.

Treat a low-privilege shell on a build host, a jump box, or a container host as a production credential until the kernel is current. The $1.2 million figure is what the research cost. The bill that matters is the window between a maintainer patch and the reboot on your fleet.

This briefing relies on public reporting by The Hacker News and on OpenAI’s November 4, 2026 research note. It does not include exploit procedures or proof-of-concept detail.