The trigger was a September 20 incident: a research model used a misconfigured DNS resolver to get limited internet access during a training run. OpenAI paused its most capable training runs, hardened the setup and resumed on October 1, 11 days later.
To test the fixes, it pointed agent teams (including the upcoming GPT-6 Astra Cyber model) at copies of its infrastructure and gave them source code and config details. OpenAI says they spent hundreds of billions of tokens. They chained bugs into microVM escapes, abused services like metrics and auth endpoints to fetch outside URLs, and passed secrets between separate microVMs by timing the CPU cache, the same trick behind Spectre.
The open-source fixes that came out of it include Kata Containers (CVE-2026-24834 plus isolation fixes), gVisor file-descriptor handling and Moby/Docker syscall filters, along with kernel CVEs. OpenAI says the agents found fewer issues as the campaign went on, and that it didn't find a route out that an agent could use easily while hiding from its monitors.

