Capability by Allowlist: Your Vendor's Lab Badge Is Now a Line Item
Three named vendors received privileged access to the model that broke OpenAI's own cyber ceiling, and the open-weights ecosystem has already routed around the fence they were meant to sit behind.
The access tiers matter more than the rating
Astra scored 100% on ExploitBench and independently discovered and chained two V8 zero-days into working exploits with no human guidance, per AI Breakfast. What changes procurement is the shape of the release rather than the benchmark. A restricted public version ships behind a runtime misalignment monitor, while the fuller cyber toolkit sits with the Daybreak Blue coalition. Anthropic executed the same structure the same day, shipping Fable 5.1 broadly while gating Mythos 5.1 to a registered partner list, per Techpresso.
Two labs converging on allowlist distribution within a day is capability governance becoming market structure. Partner status is a moat for the vendors who hold it, and an incumbent's partner status becomes a risk-register entry the buyer owns. The conflict of interest is usable rather than disqualifying. Palo Alto's CEO declared $1 trillion of installed security infrastructure not AI-ready while holding privileged access to the model driving the claim. That is excellent demand generation and the claim can still be accurate. Sizing that gap in-house costs analyst hours; letting the vendor size it costs the budget cycle.
The fence has already been walked around
Abliteration.ai shipped an unrestricted GLM-5.3 claiming double the cyber capability, per AI Breakfast. That claim is vendor-stated and unverified, and it does not need to be exact to matter. Whatever coalition boundary a lab draws, the open-weights ecosystem routes around it. Gating buys diffusion delay rather than denial. Buyers control remediation velocity, which is where the gating money should go.
The over-blocking admission is an uptime problem
OpenAI states its launch safeguards will over-block legitimate work, per Pivot 5, and the enforcement is asymmetric. In ChatGPT and Codex a flagged action pauses for human review. Through the API, the task stops. Duration and persistence are being read as misuse signals, which concentrates false-positive risk on the longest-running, most valuable agentic workloads. Agent pipelines now inherit an interrupt written by someone else's risk committee.
Where the sources diverge
| Lab | Distribution posture | Traceability | What it hands you |
|---|---|---|---|
| OpenAI | Coalition-gated cyber toolkit; restricted public tier | Weakening — recurrent depth obscures internal reasoning | An interrupt you cannot configure |
| Anthropic | Fable 5.1 open, Mythos 5.1 partner-gated | Runtime tool-call blocking; customer-held keys | Fewer false refusals, disclosed containment failures |
| No comparable frontier-cyber disclosure published | Mutable execution state — also opaque | Availability, per reported Gemini 3.8 Flash coding parity |
MIT Technology Review's read is the one to carry into planning: safety posture is shaping competitive supply. The most capable model and the most available model are no longer the same model. Every AI architecture built in the last three years quietly assumed capability access was a pricing negotiation.
The smart move
Treating capability access as a supply line with two suppliers and a written notice period is the buy-side answer, and it is cheaper than picking a lab correctly. Anyone who sat through GPU allocation already knows access widens eventually. The allocation queues also outlasted most of the roadmaps written against them. CSO First Look is right that containment is now a procurement gate, and the expensive item this quarter is the roadmap funded against a gap that closes when the next model ships.
Capability stopped being something you buy and became something you are granted, so the durable asset is the speed at which you can change who grants it.
What to do
Add frontier-lab capability access as an explicit RFP requirement and document partner status for your top five security vendors before the next renewal closes this quarter
Commission a red-team exercise this month that assumes autonomous exploit discovery and chaining, scored on detection and containment time rather than vulnerability count
Run a moat-durability review of the roadmap this quarter and cut every initiative whose only differentiation is a current model capability gap