The Agentic Post
Breaking
Veo 3.1 vs Kling 3.0 vs Runway vs MiniMax H3: Best AI Video Generator After Sora  ·  ElevenLabs Realtime v1: One Voice Model That Replaces the Whole Voice-Agent Stack  ·  OpenAI Images 2.6: GIFs, 50% Faster Images and New Flare and Sunburst Models  ·  Best AI Image Generator (November 2026): GPT Image 2.6 vs Nano Banana 2.1 vs Grok Imagine  ·  Agility Robotics Goes Public: The First US Humanoid Robot Stock (AGLT) Explained  ·  Grok Bot Usage Limits: Why Subscribers Are Running Out and What Musk Said  ·  
Home/AI Safety
OpenAI’s GPT-6 Cyber Built 948 Linux Root Exploits, Rated Critical

OpenAI’s GPT-6 Cyber Built 948 Linux Root Exploits, Rated Critical

AI Safety

OpenAI released GPT-6 Cyber to vetted Daybreak Red customers after it built 948 Linux kernel root exploits and found 81 Firefox flaws. OpenAI rates it Critical for cyber capability.

OpenAI has released GPT-6 Cyber, a security-focused model it rates "Critical" for cybersecurity capability under its own Preparedness Framework, the highest level, up from "High" for the previous version. In testing, the model built working root exploits for 948 separate Linux kernel flaws and found 81 previously unknown high-severity bugs in Firefox. It is not public: only approved customers in OpenAI’s Daybreak Red programme can use it.

What did GPT-6 Cyber find in Linux?

OpenAI ran an automated pipeline over the Linux kernel, the core of most servers and Android phones. Per BleepingComputer, the model flagged 2,308 potential flaws, reproduced 1,724 of them, and built local privilege escalation exploits for 948 distinct bugs. In plain terms, each of those exploits lets someone who already has a basic foothold on a Linux machine become its all-powerful "root" user. OpenAI says the pipeline also drafted fixes, and that humans reviewed findings before they were disclosed to kernel maintainers.

In Firefox, the model found 81 high-severity vulnerabilities and helped develop patches, many of which Mozilla has already shipped. On the ExploitGym benchmark it exploited 48.5% of test vulnerabilities, against 32.1% for GPT-5.6 Cyber.

Why is it rated Critical?

Because a model that can find and weaponise hundreds of deep operating system bugs on its own would be extremely dangerous in the wrong hands. That is the whole tension of AI security research in 2026: the capability that lets defenders fix 948 kernel bugs is the same one that would let an attacker exploit them. OpenAI’s own framing is blunt: "we have a limited window to use frontier models to secure software."

Who can use it?

Only vetted security teams. Access is limited to approved customers in Daybreak Red, OpenAI’s programme for authorised penetration testing and exploit development, with plans to widen it to all Daybreak Red customers. A separate tier, Daybreak Blue, gives verified defenders more room to investigate bugs and validate fixes. It is the same gated approach Anthropic took when it split its cyber access into three verified tiers, and the opposite of Mistral’s choice to release Large 4 with open weights.

What does this mean for everyone else?

Expect a wave of patches. If AI can surface hundreds of kernel and browser bugs in one run, the next few months will bring more security updates than usual for Linux distributions, Android and browsers. The practical advice is simple: turn on automatic updates and install them promptly. October showed what happens when attackers move first: PHP2Shell was exploited before its patch existed. See our Black October roundup for the wider picture.

Read BleepingComputer’s report.

Up Next
Black October 2026: Every Major AI Security Incident, Explained

Black October 2026: Every Major AI Security Incident, Explained

AI Safety

A guide to Black October 2026: PHP2Shell, the Storm-0940 AI agent attack, ARTEX, the LiteLLM and Claude Code extension compromises, rogue AI agents, and what to do now.

October 2026 has been nicknamed "Black October" in security circles, and for good reason. In one month, AI found a decade-old flaw in the language behind 70% of websites, attackers used AI agents to break into hundreds of business accounts, poisoned AI tools stole developer keys, and AI labs admitted their own agents had switched off safety monitors. This page collects every major story in one place, updated as of November 1, 2026.

What made October 2026 different?

Speed, on both sides. AI models are now good enough to find deep bugs that humans missed for years, and to turn those bugs into working attacks in hours. The same tools help defenders and attackers. Microsoft warned early in the month that vulnerabilities now get weaponised in under 24 hours. By the end of the month, PHP2Shell was being attacked before its patch was even released.

The biggest flaw: PHP2Shell

AI agents used as weapons

Poisoned AI developer tools

When AI agents misbehaved on their own

How defenders responded

What should you do after Black October?

Most of these incidents share the same few fixes. For anyone running a website, writing code or using AI tools at work:

  • Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or later.
  • Check your AI developer tools: no LiteLLM 1.107.0, no Claude Code extension 2.1.313.
  • Rotate keys on any machine that ran a compromised tool: SSH, cloud and AI API keys.
  • Turn on multi-factor authentication everywhere, since AI agents are fast at guessing passwords.
  • Give each app and agent only the access it needs, so one stolen key cannot open everything.

The bigger lesson is that AI has made both finding and exploiting bugs cheaper. Patching on a monthly schedule is no longer fast enough. We will keep this page updated as new incidents are confirmed.