OpenAI did not say its new model can write zero-days. It said it cannot rule that out. Only one of those sentences made the headlines.
On 7 August OpenAI published a note on Astra, an unreleased model. The wording is careful: "our preliminary evaluations indicate strong enough performance that we cannot rule out Critical capability level at this time."
Critical, in OpenAI's own Preparedness Framework, means a tool-augmented model that can "identify and develop functional zero-day exploits of all severity levels in many hardened real-world critical systems without human intervention." Previous models, GPT-5.6-Sol included, were assessed at High.
What did they do? Paused internal activities on Astra that do not meet strengthened controls: isolated testing environments, restricted network and tool access, enhanced weight protection and encryption, sandboxing.
Notice what that list is. Not deployment gating. Weight security.
Now the European part, and it is not the article you expect.
Reach for Article 55(1)(c) — report serious incidents to the AI Office without undue delay — then read the definition it leans on. Article 3(49) needs death or serious harm to health, irreversible disruption of critical infrastructure, infringement of fundamental-rights obligations, or serious harm to property or the environment.
An internal evaluation result is none of those. The clause everyone points at does not fire here.
What binds is quieter: 55(1)(a) evaluation and adversarial testing, 55(1)(b) mitigation at Union level, and 55(1)(d) — "an adequate level of cybersecurity protection for the general-purpose AI model with systemic risk and the physical infrastructure of the model." OpenAI's response reads like a worked example of 55(1)(d). And since 2 August the Commission can enforce Chapter V, fines to 3% of worldwide turnover or EUR 15 million.
What I'd do Monday:
1. Put the capability in your threat model now, at the assumed level. Voluntary disclosure moves your baseline whether you consented or not.
2. Ask your model vendor in writing for the Article 53(1)(b) and Annex XII information. It is an entitlement for downstream providers, not a favour.
3. Separate "the model is gated" from "the capability exists". Their release calendar is not your control.
4. Track mean time to patch, not open finding count. If exploit development gets cheap, latency is what kills you.
The pause is not the news. The disclosure is.
What does your threat model still quietly assume is too expensive to attack?
#AgenticAI #EUAIAct #AISecurity #GPAI #Berlin
AI disclosure: the narration voice and the cover art in this video are AI-generated. The script, the claims and the source checks are mine.