The one-screen version: two verified moves this week each exposed a dependency founders don't usually look at head-on. (1) On November 5 OpenAI launched GPT-6 Cyber, a security-tuned model that scored 48.5% on its ExploitGym benchmark (up from 32.1% a generation ago), helped find 81 novel high-severity Firefox bugs in testing, and wrote 948 working Linux-kernel exploits — and OpenAI is not releasing the weights, calling it too dangerous and gating access to vetted security teams. (2) On November 4 TeraWulf said Google backstopped the financing of a Kentucky data-center campus behind roughly $19 billion of Anthropic leases — lending Alphabet's AA+ credit, not cash, so a smaller operator can build what the lab will rent. The throughline: the thing you depend on is rarely the thing whose name is on the invoice. Here's what each one changes.
1. A model that finds real bugs — and the weights stay locked up#
On November 5 OpenAI introduced GPT-6 Cyber, a model specialized for security work: finding vulnerabilities and proposing fixes. The numbers are the story. OpenAI says it scores 48.5% on ExploitGym — its internal benchmark for whether a model can exploit a known vulnerability in a remote system — up from 32.1% for the previous GPT-5.6 Cyber, and ahead of the general-purpose GPT-6 Astra at 42.4%. In testing, the company says the model helped researchers find 81 novel high-severity vulnerabilities in Firefox, all disclosed to Mozilla and patched, and in a controlled exercise reproduced 1,724 known Linux-kernel vulnerabilities and wrote working exploits for 948 of them — roughly five times what its predecessor managed under the same conditions. It also claims a scope-control number: the model stayed on its assigned targets about 99.93% of the time.
Two caveats before you react. These are OpenAI's own figures, not independently replicated, so they're a vendor benchmark until third parties confirm them. And the Firefox and Linux work was defensive — real bugs found and fixed, which is the good version of this capability.
The part that matters more than the benchmark: OpenAI isn't releasing the weights. It frames GPT-6 Cyber as too dangerous for open distribution and gates access to vetted security teams through a program it calls Daybreak Red. That's a line this desk has watched approach for months — the ExploitGym sandbox-escape disclosure in July and the GPT-5.6 Sol egress lesson were the earlier tremors. This is the first time a lab has shipped offensive capability this strong as a product and decided the public can't have it.
The same model that finds and patches 81 Firefox bugs would weaponize them. OpenAI drew the line at open release; the capability itself did not stay behind the line.
What it changes for you: assume the code you ship now sits on dependencies that are being machine-audited at scale — by defenders who will patch faster, and, over time, by attackers who get equivalents. The practical consequence is that the window between a vulnerability becoming known and it becoming exploitable keeps shrinking, so a monthly patch rhythm is no longer conservative. The cheapest defense is to turn the same capability inward: wire LLM-assisted vulnerability scanning into your CI so you find your own holes on every push, before someone else's model does. You can't buy GPT-6 Cyber, but you don't need the frontier model to raise your own floor.
2. Google is lending its credit rating, not its cash#
The week's second move is quieter and lives one floor beneath your code. On November 4, TeraWulf announced that Google signed credit-support agreements tied to the planned debt financing of its data-center campus in Hawesville, Kentucky — backing roughly $19 billion in lease commitments from Anthropic. TeraWulf also executed a definitive EPC agreement with Fluor to build it, with phased delivery expected from late 2027 into 2028. The amount and duration of Google's support weren't disclosed; what coverage makes clear is that the support rests on Alphabet's senior-unsecured credit, rated AA+ by S&P (Cryptopolitan).
Read the structure, not the headline number. Google isn't writing a $19B check — it's lending its balance sheet so a far smaller operator can borrow at a rate it could never command alone, to build data centers that Anthropic will rent. It's the same circular-compute instinct we traced when Nvidia took a stake in a lab that buys its chips and when Anthropic financed its Theseus campus through a Macquarie-GIC joint venture: the capital, the silicon, the lab, and the landlord are increasingly the same handful of players backstopping each other. And it lands in a week when public markets turned visibly nervous about AI valuations — which is exactly when it pays to know how the financing is actually wired.
What it changes for you: when you commit a roadmap to a model vendor, you're implicitly betting that the compute behind it will be there in two years. That capacity now routinely runs through a chain — lab leases from a neocloud, the neocloud borrows against a hyperscaler's credit — where the real collateral sits several links from the name on your invoice. That's not a reason to panic; Alphabet's AA+ is about as sturdy as counterparties get. It's a reason to trace the chain before you depend on it, and to keep the model layer swappable so that a wobble three links up is an inconvenience you route around, not an outage you absorb. This is the same ledger the $895B in compute commitments in Anthropic's own filings sit on — the buildout is real, and so is the leverage under it.
The one line to take into the week#
The two stories rhyme: the exploitability of the code you ship and the creditworthiness behind the compute you rent are both dependencies you can't control and usually can't even see — and both got a little more visible this week. You can't buy the vulnerability-finding model, and you can't underwrite a data center. But you can make the exposure legible: shorten your patch cadence and scan your own code with the capability that's now cheap, and trace whose balance sheet actually stands behind your vendor before you wire your plans to it. Keep the pieces swappable, and the week's revelations are information you use rather than surprises that use you. Last edition: coding agents got cheaper, agent security got bought, and AMD bet $11B on cheaper inference.
