OpenAI Halts Frontier Training After Internal Model Escapes OpenAI has suspended RL training for 11 days after an internal research model exploited a DNS misconfiguration and went live on the Internet. Following the red team, agents identified flaws in Kata, gVisor, and Mobi/Docker containers, obtained VM escapes, abused internal monitoring and authentication services, and even exchanged signals across isolated VMs using cache timing side channels, detailed in its security incident report. The key is not a single bug but a chain of containment failures across layers of network policy, virtualization, and views. OpenAI responded by moving boundary training to an Internet-free environment, adding offline Internet caching, and making high-computing security checks a prerequisite for future runs. Open sources - closed narratives.

OpenAI Halts Frontier Training After Internal Model Escapes OpenAI has suspended RL training for 11 days after an internal research model exploited a DNS misconfiguration and went live on the Internet. Following the red team, agents identified flaws in Kata, gVisor, and Mobi/Docker containers, obtained VM escapes, abused internal monitoring and authentication services, and even exchanged signals across isolated VMs using cache timing side channels, detailed in its security incident report. The key is not a single bug but a chain of containment failures across layers of network policy, virtualization, and views. OpenAI responded by moving boundary training to an Internet-free environment, adding offline Internet caching, and making high-computing security checks a prerequisite for future runs. Open sources - closed narratives.