← All AI resources

Google DeepMind · Gemini 4 Carbon cyberdefense launch guide

Gemini 4 Carbon puts cyber defenders first in a restricted rollout

Google reports large gains in vulnerability discovery, exploitation and patching, while independent testing places Carbon near the top of a broad capability index.[1][7] Carbon now has a documented API and model card, while enhanced cyber access remains controlled through Fairwind.[3][8]

Published by Learnetto team · Published October 28, 2026 · Updated November 19, 2026

Gemini 4 Carbon · October 28, 2026

Three cyber stages, one restricted rollout

Find

88.2%

SEC-bench Pro

Validate

54.8%

ExploitGym

Repair

71.0%

CWE-bench

Access: selected cyber defenders first through Fairwind
Google evaluated the three cyber benchmarks without guardrails. Teams should test discovery, exploit validation and patch acceptance separately under the controls they will use.

Google announced Gemini 4 Carbon two weeks after Argon and initially gave selected cyber defenders access through Fairwind.[1] The company reports 88.2% on SEC-bench Pro, 54.8% on ExploitGym and 71.0% on CWE-bench, all evaluated without guardrails.[1] Google now documents Carbon across the Gemini API, AI Studio, Gemini for business and other product surfaces, while its cyber-permissive variant remains limited to approved Fairwind projects.[8][9] Security teams can evaluate the standard model now, but enhanced cyber use still requires separate access controls and matched safety testing.

Initial access
Selected cyber defenders
SEC-bench Pro
88.2%
ExploitGym
54.8%
CWE-bench
71.0%

What Google announced

Google introduced Gemini 4 Carbon on October 28 [1]. Google calls it the company's strongest model and says internal teams have run it for days on difficult engineering tasks.

Google started with a subset of cyber defenders and planned to add trusted partners through Fairwind while testing safeguards.[1] Reuters also reported the restricted rollout, security focus and proposed introductory token prices.[2] Carbon is now distributed through the Gemini API, AI Studio, Gemini for business, Antigravity, AI Mode and the Gemini app, with access varying by product and subscription.[9]

The Gemini API charges $2 per million input tokens and $10 per million output tokens through November 30, 2026, then $4 and $20 respectively from December 1. Cached input costs $0.10 per million tokens during the introductory period and $0.20 afterward; output pricing includes thinking tokens.[10]

Read the three cyber scores separately

Google reports 88.2% on SEC-bench Pro for vulnerability discovery, 54.8% on ExploitGym for exploitation and 71.0% on CWE-bench for patching.[1] Google ran these external cyber evaluations without guardrails.[1] Product safeguards may change what approved users can reproduce.

Each score answers a different question. A suspected bug still needs validation, and a working exploit still needs a tested repair. Security teams should preserve that sequence instead of treating one aggregate score as proof that Carbon can run an end-to-end vulnerability program.

At launch, Google's announcement said Carbon ranked first [1] on the v5.0 Artificial Analysis Intelligence Index with a score of 59. The index combines evaluations across knowledge work, coding, science and general knowledge; later index revisions and task-specific results should be evaluated separately.

VentureBeat's benchmark review [6] found a mixed picture beneath the headline. Carbon improved over Argon across Google's table, while GPT-6 Astra remained ahead on FrontierSWE 2 and Claude Opus 5.5 remained ahead on one OSWorld computer-use result.

What Google says about agent safety

Google says Carbon uses the safety stack developed for Argon: model training, real-time misuse defenses, prompt-injection resistance and reasoning monitors.[1][4] The company reports no successful cheating on its Terminal-Bench 4.0 test, a 0.4% attempt rate and no successful attack in the evaluated Gray Swan indirect prompt-injection set.[1] Those results cover defined tests and do not prove immunity in an unfamiliar repository or browsing session.

Google's Carbon safety report [5] says Google cannot rule out that unmitigated Carbon reaches its cyber and biological critical-capability thresholds. Google says its safeguards reduce residual risk below those thresholds; the report also found no material capability change requiring a new full critical-capability assessment.

Google's Carbon model card [9] reports stronger multilingual and text safety results than Argon, while warning that Carbon can still hallucinate, run slowly or time out, and consume more tokens at higher reasoning levels. The Carbon safety report separately records improved agent behavior and details the evaluation methods and mitigations.[5]

A defensible evaluation plan

  • Write down the authorized repositories, systems, test accounts and network ranges before requesting access. Exclude customer and production targets unless the owner has approved the exact test.
  • Build three task sets: known vulnerable code for discovery, isolated challenge systems for exploit validation and repositories with regression tests for patching. Score each stage independently.
  • Run Argon or the current approved tool on the same tasks. Compare true findings, false positives, exploit validity, patch acceptance, elapsed time, token use and reviewer hours.
  • Keep exploit validation inside an isolated environment with no production credentials, unrestricted internet access or route to unrelated systems.
  • Require a human reviewer to confirm the vulnerability, inspect every command and approve each patch before merge. Run security tests and the existing regression suite after every accepted change.
  • Seed repositories and documents with benign prompt-injection canaries. Confirm that the agent ignores them, reports them and does not expose secrets or change scope.
  • Record refusals and blocked actions as part of utility testing. Google's unguarded benchmark scores may differ from the behavior available through Fairwind or a later public product.[1]
  • Set a stop rule for unexpected egress, privilege changes, scope expansion, fabricated evidence or attempts to alter evaluation infrastructure. Preserve logs for review.

Fairwind changes the operating conditions

The Fairwind program page [3] says participating organizations must use user-level authentication, phishing-resistant multi-factor authentication and applicable access controls. They must restrict access to internal security, incident-response or penetration-testing teams and track employee use.

Fairwind can give verified defenders access to the cyber-permissive model that standard Gemini access restricts.[3][8] That difference means a result from an approved defensive environment may not describe the consumer or standard API product.

Teams should ask Google which Carbon model snapshot they receive, which safeguards apply, where data and logs are stored, how access can be revoked and what evidence remains available after an incident. The developer guide identifies gemini-4-carbon-cyber-permissive as the Fairwind model ID, but project-specific contract and operating terms still need direct confirmation.[8]

What remains uncertain

  • Google now documents Carbon's model ID, unified 1,048,576-token input-output limit, API conventions and product distribution.[8][9] Teams should still test the exact product surface because access, regions and controls vary by channel.[9]
  • Google says its Chrome team produced high-quality patches at more than ten times the rate of an unnamed competing model. The release materials do not identify that model or provide the underlying results for independent review.[1]
  • The cyber benchmark scores were measured without guardrails, so approved and public deployments may produce different results.[1]
  • Artificial Analysis captured availability at launch. Current Google documentation now lists API access, so teams should use dated evaluator snapshots for benchmark context rather than procurement status.[7][8]
  • A 0.0% attack-success result means the evaluated prompt-injection attacks failed. New attack paths, tools and environments still require testing.[1]
  • Google says internal teams ran Carbon for days, but it has not published completion rates, intervention counts, resource use or incident data for those runs.[1]

Frequently asked questions

  • Can developers use Gemini 4 Carbon now? Yes. Google documents the gemini-4-carbon API model. Enhanced cyber access through gemini-4-carbon-cyber-permissive remains subject to Fairwind approval.[3][8]
  • Is Carbon a replacement for Argon today? Carbon is now documented for API use, but teams should migrate only after matched quality, cost and safety tests.[8]
  • Does Carbon find and fix every vulnerability? No. Google's three published cyber scores all remain below 100%, and each covers a defined evaluation.[1]
  • Are the security scores independently verified? Artificial Analysis independently reports the broad index result. Google reports the three cyber scores and says it ran them without guardrails.[1][7]
  • What should a security team test first? Start with known vulnerable code in an isolated environment, then measure valid findings, false positives, working patches and human review time.
  • Does the 0.0% prompt-injection result remove the need for sandboxing? No. It describes one evaluated attack set, while real repositories and tools can expose different instructions and permissions.[1]

Keep learning on Learnetto

Sources

[1] Google: Gemini 4 Carbon announcement

[2] Reuters: Carbon launch and rollout summary

[3] Google DeepMind: Fairwind Program

[4] Google: Gemini 4 safety overview

[5] Google DeepMind: Gemini 4 Carbon Safety and Security Report

[6] VentureBeat: independent benchmark and availability analysis

[7] Artificial Analysis: Intelligence Index v5.0

[8] Google Cloud: Gemini 4 Carbon developer guide

[9] Google DeepMind: Gemini 4 Carbon model card

[10] Google AI Studio: Gemini API pricing