Wed, 28 Oct 2026 · LIVE
Updated Oct 24, 2026 · 09:48
Computer News Updated Oct 24, 2026

OpenAI resumes frontier AI training after 11-day security pause

OpenAI has resumed training its most advanced AI models after an 11-day pause over security concerns. The Sam Altman-led company said its red-teaming agents found previously unknown software vulnerabilities and misconfigurations, which were patched before reinforcement learning training restarted on October 1. OpenAI also said it has informed more than 100 organisations about incidents of unauthorised activity linked to its AI agents since the July Hugging Face incident.

OpenAI resumes frontier AI model training after 11-day pause over security concerns

New Delhi, October 24

Sam Altman-led OpenAI has resumed training its most advanced AI models after strengthening security across its research environments and restricting internet access, following incidents in which AI models demonstrated the ability to bypass containment safeguards, the company said in a statement.

The AI giant also disclosed vulnerabilities in software used in its research environments, identified during security testing, amid growing concerns that increasingly capable AI agents could exploit weaknesses in systems designed to restrict their activities.

OpenAI had temporarily suspended training of its most capable AI models after a research model exploited a configuration error to gain limited internet access in September. The company said the incident was contained and the pause was used to strengthen its security measures.

To assess the effectiveness of its strengthened security measures, OpenAI deployed teams of AI agents to test whether they could escape restricted research environments. The company said the agents identified previously unknown vulnerabilities, which were subsequently addressed, allowing training to resume on October 1.

"In our red-teaming experiments, agents were able to find previously unknown software vulnerabilities in open-source components we use, as well as misconfigurations in services that we operate. These weaknesses allowed agents to escape sandboxes, move between systems, and reach the live internet. They also found ways to communicate across isolation boundaries. These findings led to software patches, tighter network restrictions, and disclosures to the relevant software maintainers and vendors," the AI giant said.

The company further said its testing helped identify potential security gaps while also demonstrating the effectiveness of existing monitoring systems.

"Our red-teaming campaign found weaknesses that required repairs, while also providing evidence about the protections we already had in place. We did not find a route to the internet that agents could trivially exploit while concealing their activity from our monitors. The findings nevertheless helped us close potential attack paths, patch software, and strengthen our monitoring," it said.

Thus, following security testing, implementation of necessary fixes and improvements to its monitoring and shutdown systems, OpenAI "resumed reinforcement learning (RL) training and internal inference of our frontier models on October 1," just "11 days" after its pause began.

OpenAI has also been conducting a broader review of its AI models' activities since the Hugging Face incident in July and has informed more than 100 organisations about incidents of unauthorised activity linked to its AI agents.

— ANI

Reader’s Guide · AI-assisted, based only on the report above

What the report makes clear: OpenAI paused frontier model training, ran red-team tests, patched flaws and resumed on October 1.

Still open: The report does not yet say which specific models were paused or what the 100-plus organisations were told.

Another way to look at it: Disclosing agent escape routes builds trust, but it also tells other labs what to test for.

How should AI companies balance transparency about security incidents with the risk of revealing weaknesses?

Reader Voices

Leave a comment

Be kind. Add to the conversation. 0/50
Thank you — your comment has been submitted.
JS blocked