Google Rapidly Iterates Gemini with 3.6 Flash Family and Restricted Cybersecurity Variant · history
Version 2
2026-07-22 18:20 UTC · 34 items
What
Google released Gemini 3.6 Flash and 3.5 Flash-Lite on July 21, 2026, deprecating 3.5 Flash just two months after its Google I/O debut [2][1]. A cybersecurity-specialized variant, 3.5 Flash Cyber, was announced July 17 and restricted to governments and trusted partners due to its ability to autonomously find and exploit production vulnerabilities [3]. The Verge and CyberNews positioned Flash Cyber as a cheaper alternative to larger dedicated AI security models, naming Mythos as a reference point [4][5]. Gemini 3.5 Pro remains unshipped, held back by coding performance shortfalls, with multiple outlets now offering theories on the delay [8][9][10][11].
Why it matters
Google is cycling through Flash models faster than typical product timelines while a coding quality shortfall keeps its Pro-tier model from shipping. Flash Cyber's framing as a cheaper entry in the AI security model market — against larger dedicated models — suggests Google sees commercial opportunity there, though the model can generate working exploits and relies on access controls rather than capability limits as its safeguard.
Open questions
When will Gemini 3.5 Pro ship, and what specific coding benchmarks must it clear before Google releases it? [6][9][10]
Did Google's efficiency-first training approach directly cause 3.5 Flash's coding underperformance, and has that priority changed with 3.6 Flash? [2]
Will access to 3.5 Flash Cyber expand beyond governments and trusted partners, and what criteria would govern that expansion? [3][4]
How does Flash Cyber compare to dedicated large AI security models like Mythos in real-world engagements, beyond Google's own benchmark framing? [4][5]
Narrative
Google released three new Gemini models on July 21, 2026, reorganizing its Flash tier and introducing a restricted cybersecurity variant. Gemini 3.6 Flash replaces 3.5 Flash — which had been the centerpiece of Google I/O just two months earlier — claiming 17% fewer output tokens while improving on benchmark areas where 3.5 Flash underperformed, including DeepSWE coding (49% vs. 37%) and OSWorld computer use (83.0% vs. 78.4%) [1]. Gemini 3.5 Flash-Lite, released the same day, targets high-volume latency-sensitive workloads, reaching 350 output tokens per second while outperforming Gemini 3 Flash on SWE-Bench Pro (54.2% vs. 49.6%) [1]. Ars Technica noted the unusual pace of 3.5 Flash's deprecation and argued Google's intense focus on token efficiency for enterprise cost reasons may have contributed to the original coding shortfall that 3.6 Flash was built to address [2].
Four days before the Flash releases, Google announced Gemini 3.5 Flash Cyber, trained specifically for offensive and defensive security work. In internal evaluations, it found 55 unique confirmed vulnerabilities in Chrome's V8 JavaScript engine, compared to 47 by mainline 3.5 Flash and 36 by Claude Opus 4.6 [3]. In a two-hour test on Google's own production systems, it uncovered remote code execution vulnerabilities in public APIs and a memory-corruption flaw in a sensitive service, then generated a functional RCE exploit bypassing both ASLR and W^X mitigations [3]. Google is limiting the model to governments and trusted partners through its CodeMender platform, treating access controls rather than capability reduction as the appropriate safeguard. The Verge and CyberNews framed the model as a cheaper alternative to larger dedicated AI security models, specifically naming Mythos as a cost comparison point [4][5].
Running alongside the Flash releases is the unresolved delay of Gemini 3.5 Pro, which had been expected to launch in June. Bloomberg reported that Google held the model back because coding performance fell short of internal targets, and Alphabet's share price fell on that report [6][7]. Multiple outlets have since published analysis and theories on the delay [8][9][10][11], though Google's own public communications have addressed the Pro situation only briefly and without specifics. Separately, Google disclosed it has begun what it called its most ambitious pre-training run yet for Gemini 4, with no timeline or capability claims attached [1].
Timeline
- 2026-05: Google I/O: Gemini 3.5 Flash announced as the flagship model [2]
- 2026-06: Gemini 3.5 Pro expected to launch but does not ship [12][6]
- 2026-07-16: Bloomberg reports Gemini 3.5 Pro delayed due to coding performance shortfall; Alphabet shares fall [7][6]
- 2026-07-17: Google announces Gemini 3.5 Flash Cyber, restricted to governments and trusted partners via CodeMender [3]
- 2026-07-21: Google releases Gemini 3.6 Flash and 3.5 Flash-Lite, deprecates 3.5 Flash, and discloses Gemini 4 pre-training has begun [1][2][13]
- 2026-07-21: The Verge and CyberNews frame Flash Cyber as a cheaper alternative to large dedicated AI security models like Mythos [4][5]
- 2026-07-22: Multiple outlets publish analysis and theories on why Google delayed Gemini 3.5 Pro [8][9][10][11]
Perspectives
Google DeepMind
Presents 3.6 Flash as an efficiency and capability improvement over 3.5 Flash, frames Flash Cyber's vulnerability-finding results as evidence for a lightweight multi-invocation approach to security AI, and argues CodeMender access controls are the right mechanism for managing dual-use risk.
Evolution: Consistent promotional framing; the 3.6 Flash release implicitly acknowledges 3.5 Flash underdelivered on coding without stating it directly.
Ars Technica (Ryan Whitwam)
Reports the releases factually while arguing Google's efficiency-first training priorities may have caused 3.5 Flash's coding shortfall, and notes the awkward optics of deprecating a two-month-old flagship model.
Evolution: No prior stance in this thread; first analysis from this outlet.
The Verge / CyberNews
Frame Flash Cyber primarily through a market-positioning lens — as a cheaper, smaller alternative to large dedicated AI security models like Mythos — rather than through the access-control or dual-use framing Google emphasizes.
Evolution: New voices in this thread; their competitive framing differs from Google's own capability-and-safety narrative.
Tensions
- Google presents 3.6 Flash's gains as straightforward improvement; Ars Technica argues Google's cost-reduction focus may have produced the coding underperformance in 3.5 Flash that 3.6 Flash is now correcting. [2][1]
- Google frames Flash Cyber's restricted access via CodeMender as the appropriate safeguard for a model that can generate working exploits; The Verge and CyberNews frame the same model primarily as a cheaper market entrant relative to dedicated security AI, implicitly downplaying the dual-use risk framing. [3][4][5]
- Google's public statements on the 3.5 Pro delay offer no specifics; Bloomberg's reporting on coding shortfalls, confirmed by a share-price reaction, gives the delay a clearer cause than Google has acknowledged. [6][7][1]
Sources
- [1] Introducing Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber — DeepMind Blog (2026-07-21)
- [2] Google announces Gemini 3.6 Flash and cybersecurity AI, teases 3.5 Pro and Gemini 4 — Ars Technica AI (2026-07-21)
- [3] Introducing Gemini 3.5 Flash Cyber — DeepMind Blog (2026-07-17)
- [4] Google launches a cheaper alternative to large AI security models like Mythos — reactive:google-gemini-36-launch
- [5] Google debuts smaller, cheaper Gemini Flash AI cybersecurity model — reactive:google-gemini-36-launch
- [6] Gemini 3.5 Pro Delayed Over Coding, Bloomberg Reports — reactive:google-gemini-36-launch
- [7] Alphabet shares fall on report its AI model Gemini 3.5 Pro is delayed — reactive:google-gemini-36-launch (2026-07-21)
- [8] Google Delays Gemini 3.5 Pro Due to Coding Goals | Learnijoy NewsCenter — reactive:google-gemini-36-launch
- [9] Google Gemini 3.5 Pro faces "delays" over coding performance misses - Neowin — reactive:google-gemini-36-launch
- [10] Gemini 3.5 Pro Delay: Why Google Postponed Its AI Again - Geeky Gadgets — reactive:google-gemini-36-launch
- [11] Google Delayed the Gemini 3.5 Pro AI Model. Here's a Theory on Why. - Business Insider — reactive:google-gemini-36-launch
- [12] Gemini 3.5 Pro delays due to coding performance — reactive:google-gemini-36-launch
- [13] Gemini 3.6 Flash released on AIStudio — reactive:google-gemini-36-launch (2026-07-21)