Skip-Level
OpenAI Agents Built Working Exploits for 948 Linux Kernel Bugs
By Steven Sorensen ยท 5 Nov 2026

- OpenAI says an agent pipeline built working root exploits for 948 Linux kernel bugs in one run.
- Meta has acquired Conductor, and its cloud service shuts down on November 20.
- OpenAI will acquire Pierre Computer to bring its Git tooling into Codex.
- Gartner finds only 4% of CIOs have plans to redesign roles for people working with AI agents.
Three things engineering and IT managers should know this Thursday, from a step change in how fast kernel bugs are found to who now owns the tools your developers use to run coding agents.
1. OpenAI Agents Built Working Exploits for 948 Linux Kernel Bugs
OpenAI published research on Nov 4 describing an autonomous pipeline, built on an upcoming cyber model, that finds, reproduces, exploits, and drafts patches for Linux kernel vulnerabilities. In a run in mid October, the pipeline produced 2,308 candidate findings, reproduced 1,724 vulnerabilities in isolated virtual machines, and generated 948 working local privilege escalation exploits that let an unprivileged local user gain root on a commonly used Linux distribution. The target machines ran a stock desktop operating system with standard protections switched on. OpenAI puts the total cost at $1,213,430 in API credits, or $1,279 per exploit, and calls its cost figures an upper bound. Human researchers review each exploit, patch, and severity rating before anything goes to maintainers. OpenAI says it has already sent hundreds of reports and patches for critical vulnerabilities and is working with partners on the rest. It also reports that by the time its scan and analysis finished, 61 of the bugs had been patched upstream and 43 had staging patches. The company adds that its newer model found more than five times as many novel privilege escalation bugs as a July run, despite three months of kernel hardening between the scans.
Why it matters: OpenAI's own guidance is blunt. For the near and medium term, it says a low privileged account on a system that is behind on patches should be treated as functionally equivalent to root for a well resourced attacker. Our read: the bottleneck for your team is no longer finding kernel bugs but shipping the fixes. Ask your platform and security leads how quickly kernel updates reach your fleet today, where shared multi user Linux hosts and build runners sit, and whether sandboxing limits the damage if a local account is compromised. Expect a larger than usual stream of kernel patches over the coming weeks and plan reboot windows for it. Source: OpenAI
2. Meta Buys Conductor as OpenAI Moves to Acquire Pierre
Meta has acquired Conductor, a startup whose tool lets developers run several coding agents in parallel workspaces, TechCrunch reported on Nov 4. The agents it runs come from labs such as Anthropic and OpenAI rather than being built in house. Meta confirmed the deal but gave no terms. Conductor's founder said core features will keep working as before until early next year, with one exception: Conductor's cloud service shuts down on November 20, after which the company will begin deleting user cloud data. The same day, OpenAI announced it will acquire Pierre Computer Company, the maker of Code Storage and the Trees and Diffs libraries already used in the Codex app. OpenAI says Pierre's open source projects will stay open source and Code Storage customers can keep using it after closing while its features move into Codex. The deal still needs regulatory approval, and Axios reported that the deal puts OpenAI among the companies challenging Microsoft's GitHub.
Why it matters: The layer that sits between your developers and their coding agents is being bought by the large labs. Our read: if anyone on your team uses Conductor Cloud, there are about two weeks to export work before the shutdown and data deletion, so check now. More broadly, list the agent orchestration and code hosting tools your teams depend on, note which vendor owns each one today, and decide where you would accept tighter lock in to a single lab. Sources: TechCrunch and OpenAI
3. Few CIOs Have a Plan to Redesign Roles Around AI Agents
A Gartner survey of 2,002 CIOs and technology executives for its 2027 agenda report, covered by CIO Dive when it was released on Oct 19, found that just 4% have plans in place to redesign roles for a workforce of people and AI agents. Organizations with such plans are 2.4 times more likely to be top performers with AI and to have CEOs who report value from it. The same survey found 58% of leaders face growing pressure to show cost improvements from earlier AI investments, while only 13% report significant or transformational value from AI so far. Gartner analyst Alicia Mullery told CIO Dive that cost pressure often pushes workforce planning down the list.
Why it matters: This is survey data, and the 2.4 times figure shows an association rather than proof that redesign causes better results. Our read: for engineering managers the practical step is small. Pick one team, write down which tasks agents now handle, which roles have grown to cover review and oversight, and what that means for hiring and career paths, then share it with your own manager. Source: CIO Dive
Compiled daily with Grok from public sources and edited by the AIDevPulse team.
Get Skip-Level and the daily brief in your inbox: sign up for the AIDevPulse newsletter. For today's developer news, read today's main brief.
Sources:
- OpenAI: A thousand fewer paths to root
- TechCrunch: Meta acquires AI coding startup Conductor
- OpenAI: OpenAI to acquire Pierre Computer Company, Inc.
- CIO Dive: CIOs unprepared for agentic workforce shift
Recommended AI prompt
Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.
I manage an engineering or IT team. Using only the three items in this readout, help me draft a one page plan for the next month that does three things: lists the questions I should ask my platform and security leads about how fast kernel patches reach our Linux systems and where local accounts could be escalated to root, inventories the coding agent and code hosting tools my team relies on and who owns each vendor today, including any Conductor Cloud data we need to export before November 20, and outlines how one team's roles have changed now that agents handle part of the work. Keep my team's context in mind: [describe your team's size, the Linux systems you run, and the AI coding tools you use today]. Do not add facts that are not in the readout, and flag anything I should check before sharing.