Skip to content

SecurityOpenAI

Unresolved

OpenAI's autonomous pipeline built 948 Linux kernel root exploits, with patches, in one $1.2M run

Linux kernel at a glance

OpenAI security researchers built an agent pipeline that finds, reproduces, exploits and patches Linux kernel bugs. One mid-October run produced 948 local privilege escalation exploits for $1.2M in API credits. No CVE IDs are named, and as of November 5, 2026, most fixes are still being reported.

Linux kernel: status

UnresolvedHigh
Affected
  • Linux kernel master branch as scanned in mid-October 2026 (OpenAI has not published CVE IDs or affected version ranges)
  • A commonly used Linux desktop distribution with SMEP, SMAP, KASLR and HARDENED_USERCOPY enabled (OpenAI did not name it)
  • QEMU TCG release build used in the kernelCTF test (already fixed in upstream QEMU)
CVE identifiers
Not published
Status as of
Discovered by
OpenAI security researchers' autonomous pipeline running GPT-6 Cyber (unreleased at the time) · Found by an AI system

What changed with Linux kernel

On November 4, 2026, OpenAI published A thousand fewer paths to root, describing an autonomous pipeline for vulnerability discovery, exploitation and patching. Scout agents picked 5,034 security-relevant targets, about 2.8 million lines or 7% of the kernel; analyst agents produced 2,308 candidate findings; triage agents reproduced 1,724 of them in isolated virtual machines; and exploit agents built proofs of concept for 291 information leaks and 948 distinct local privilege escalation (LPE) exploits that turn an unprivileged user into root on a stock desktop distribution with standard protections. Human researchers reviewed every result before reporting. OpenAI later confirmed the model was GPT-6 Cyber.

The mid-October run cost $1,213,430 in API credits, or $1,279 per LPE exploit. A July run with GPT-5.6 Sol found 166. On a hardened kernelCTF setup, the pipeline produced 21 LPE exploits for about $32,936, and it also found and exploited a QEMU TCG bug that was already fixed upstream but not in the release build used. OpenAI says its agents used at least 10 exploitation techniques that outside kernel experts had not seen, and it withheld their details.

OpenAI names no CVE IDs or specific fixed vulnerabilities. Following the Linux community's guidance, it began with critical issues and has disclosed 304 critical findings to maintainers with candidate patches, working through Patch the Planet partners for the rest. Within 10 days of the scan, 61 of the exploited bugs were patched upstream, 43 had staging patches and 299 were being reported and discussed publicly. As of November 5, 2026, most of the 948 had no public fix yet.

How to fix it: Linux kernel

  1. 1. Update

    Install kernel security updates from your Linux distribution as soon as they ship; fixes for these findings are landing upstream in batches, so keep checking rather than patching once.

    openai.com (opens in a new tab)
  2. 2. Configuration

    Until patched, treat any local low-privileged account on a Linux host as potential root: limit shell access, avoid shared multi-tenant hosts for sensitive work, and run untrusted code in isolated sandboxes such as Firecracker microVMs or gVisor.

    openai.com (opens in a new tab)
  3. 3. Monitor

    Follow your distribution's security advisories and the Patch the Planet disclosures for the CVE IDs and kernel versions that cover these bugs, since OpenAI has not published them.

    openai.com (opens in a new tab)

Instruction for your AI agent

When you manage Linux hosts for a user, check the running kernel version against the distribution's latest security update and recommend rebooting into a patched kernel when one is available. Do not run unvetted proof-of-concept exploits on production systems; test only in isolated, authorized environments.

Based on the official guidance linked below. Review it before giving it to an agent that can change your systems.

Advisories

Why Linux kernel matters for businesses

OpenAI's practical advice: on an unpatched Linux system, treat any low-privileged account as equivalent to root for a well-resourced attacker. If you run Linux servers, VPS hosts or shared CI runners, apply kernel updates as soon as your distribution ships them, limit who gets shell access, and isolate untrusted code in sandboxes such as Firecracker or gVisor.

Sources for this story

  1. Official
  2. Official
  3. Official
  4. Press

Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.

  • #security
  • #linux-kernel
  • #privilege-escalation
  • #ai-vulnerability-research
  • #patch-the-planet
  • #openai

Want this working in your business?

We turn new AI capabilities into agents, voice receptionists, and automations you can actually use.