OpenAI report, A thousand fewer paths to root, published November 4, 2026; run conducted mid-October 2026
948 Paths to Root in One Run: an OpenAI Pipeline Exploited and Drafted Patches for 948 Linux Kernel Flaws
OpenAI reported on November 4 that an autonomous pipeline built on an upcoming cyber model validated and generated patches for 948 distinct local privilege escalation vulnerabilities in the Linux kernel in a single mid-October run, at a total API cost of $1,213,430. The funnel is stated in full: scout agents selected 5,034 audit targets covering about 7 percent of the kernel; analyst agents produced 2,308 candidate findings; triage in virtual machines with Kernel Address Sanitizer reproduced 1,724 of them; exploit development agents working against standard distribution protections produced 1,169 working exploits and 291 information leak proofs of concept, which variant analysis reduced to 948 distinct vulnerabilities, each with a candidate patch. OpenAI puts the cost at about $1,279 per distinct vulnerability and about $359 per successful exploit, and values the set at $18.9 million to $66.3 million against historical Pwn2Own and TyphoonPWN bounty rates. All of these figures are OpenAI's own accounting and have not been independently verified, and the 948 are validated exploits with candidate patches, not shipped fixes: when the scan and manual review finished, 61 had been patched upstream, 43 had staging patches, and about 299 were being reported and discussed publicly, with the rest being submitted in stages through the Patch the Planet program. The trajectory matters as much as the total. The same program produced 24 working exploits in June and 166 in a July run with GPT-5.6 Sol, so the October run is more than five times the July result despite three months of kernel hardening in between. OpenAI also says the agents used at least 10 exploitation techniques outside experts had not seen, and it is withholding those details. Its guidance to defenders is blunt: a low-privileged account on an unpatched system should be treated as functionally equivalent to root for a well-resourced actor.
Executives
The economics of vulnerability discovery just moved in public, with a price attached: roughly $1,279 per distinct kernel privilege escalation in the operator's own accounting, against a historical bounty value many times higher. The same pipeline in defensive hands produces patches; in offensive hands it produces a stockpile. Either way, the planning assumption that a low-privilege foothold is a contained problem is no longer safe on unpatched Linux. Ask what your patch latency is for kernel updates specifically, because that number is now the exposure window.
CIO / CISO
Adopt OpenAI's own framing as an internal rule: on an unpatched Linux system, a low-privileged account is treated as equivalent to root for risk purposes. That changes triage for every finding that grants any local access, including web shells and container escapes. Shorten kernel patch cycles, track the upstream flow from this disclosure as the candidate patches land in stages, and add rescanning of previously audited code to the program, since the report's other lesson is that each model generation finds materially more in code that was already reviewed.
Engineers
Patch kernels on the distribution's security channel and verify the running kernel after reboot, since installed packages do not protect a system still booted on the old build. Where patch windows are slow, lean on the isolation controls OpenAI names: sandboxing with tools such as Firecracker and gVisor, strict least privilege for service accounts, and no shared low-privilege access on multi-tenant hosts. Watch for the staged Patch the Planet submissions for your subsystems rather than waiting for a single disclosure event.
Everyone (non-IT)
If you run Linux at home, on a home server, or on a small cloud instance, keep it updated and reboot after kernel updates so the new kernel actually loads. Nothing in this story requires a new tool or a new purchase. It does mean that an old, forgotten virtual machine with an account anyone can reach is a bigger liability than it used to be, because the cost of turning small access into full control is falling.