Gemini 4 Carbon: What Defenders Should Know About Google's Newest Model

Posted on Oct 30 • Originally published at trevorheshka.com

Draft by Trevor Heshka, IT Support · Cybersecurity · Full-Stack & AI, Nanaimo BC

Two weeks after Gemini 4 Argon, Google announced Gemini 4 Carbon on October 28, 2026. Google calls it its strongest model, and the launch post puts cybersecurity front and centre. If you defend networks or handle IT for small businesses, that cuts both ways. A model that's better at finding and patching vulnerabilities is also better at finding them for someone else. This post covers what Carbon is, who can use it right now, what Google says about its security and safety, and how I'd think about it in a small IT shop.

Carbon is Google's next frontier model after Argon, built for long-horizon coding and agentic work and for cybersecurity defense. Google says its internal teams have seen Carbon run for days on hard engineering problems, working through dead ends to root-cause and patch subtle bugs across large codebases and low-level systems.

The big difference from Argon is the rollout. Most of us can't call Carbon yet. Google says it's taking part in the U.S. government's voluntary pre-release model testing process and is starting with defenders before anyone else gets access.

Google says Carbon covers the whole defense lifecycle: finding vulnerabilities, confirming which ones are exploitable, and fixing them. These are the external benchmark results it reports (evaluated without guardrails):

"Without guardrails" is important. Those scores show what the raw model can do, not what the public version will help you with once it ships with safeguards.

The exploitation score is the one to sit with. A model that can turn more than half of the bugs it's given into working exploits helps a defender decide what to patch first. It's also why Google is gating access.

Carbon uses the same layered safety stack as Argon: model training, real-time misuse defenses, prompt-injection resilience and chain-of-thought monitoring. Google says it pushed harder on alignment this time, especially for complex or high-pressure tasks. What it reports:

Those are strong numbers. Still, 0.0% on a benchmark means it resisted every attack in that test set. It doesn't mean nobody can inject it. Attackers will write new attacks, and an agent reading email or web pages still faces input nobody has tested. Build your setup on the assumption that something will eventually get through.

Carbon isn't on the public API yet, so I'm not going to guess at code. When it reaches developers, check Google's Gemini API docs for the model ID and settings rather than copying from a launch post. The ground rules I'd use don't depend on which model you're running:

Most of the businesses I support around Nanaimo and Vancouver Island have one IT person, or someone like me on call. For now, Carbon matters to them mostly in two ways.

Carbon looks like a real step forward for defenders, and I like that Google is releasing it to defenders first and publishing specific safety numbers. The trade-off is that most small shops will have to wait. In the meantime, the job is the same: know what you have exposed, patch quickly, and check what the AI tells you before you act on it.

If you're a small business on the Island and want a second set of eyes on what's exposed, I'm happy to help.