OpenAI says planned GPT-6.1 is too insecure to release
Back to the drawing board OpenAI says planned GPT-6.1 is too insecure to release Similar performance, security tradeoffs also seen in current public models. Kyle Orland – Sep 29, 2026 10:22 am | 6 Not so fast, GPT-6.1... The move, first reported by The Wall Street Journal late Monday and later confirmed in OpenAI statements to the press, reflects what OpenAI Head of Safety Systems Saachi Jain said was a “trade off” between performance and security seen when testing the now-scrapped model.
- ▪Back to the drawing board OpenAI says planned GPT-6.1 is too insecure to release Similar performance, security tradeoffs also seen in current public models.
- ▪Kyle Orland – Sep 29, 2026 10:22 am | 6 Not so fast, GPT-6.1...
- ▪The move, first reported by The Wall Street Journal late Monday and later confirmed in OpenAI statements to the press, reflects what OpenAI Head of Safety Systems Saachi Jain said was a “trade off” between performance and security seen when
2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Ars Technica files mainly under tech. We currently carry 393 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ars Technica |
| Canonical URL | https://arstechnica.com/ai/2026/09/openai-says-planned-gpt-6-1-is-too-insecure-to-release/ |
| Publication time | Tue, 29 Sep 2026 14:22:31 +0000 |
| Retrieval time | 2026-09-29T14:41:38.660Z |
| Last seen | 2026-09-29T14:41:38.660Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 6hubCbbklJ9I · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back to the drawing board OpenAI says planned GPT-6.1 is too insecure to release Similar performance, security tradeoffs also seen in current public models. Kyle Orland – Sep 29, 2026 10:22 am | 6 Not so fast, GPT-6.1... Credit: Getty Images Not so fast, GPT-6.1... Credit: Getty Images Text settings Story text Size Small Standard Large Width * Standard Wide Links Standard Orange * Subscribers only Learn more Minimize to nav OpenAI says it has canceled plans to release its updated GPT-6.1 model next month as it continues to investigate what testing shows to be a regression in terms of safety compared to previous models.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ars Technica.
Discussion
0 commentsMore from Ars Technica
