Google Gemini gemini-2.0-flash-lite · Version Status

Google Gemini gemini-2.0-flash-lite End of Life Date

Google Gemini gemini-2.0-flash-lite end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Google Gemini gemini-2.0-flash-lite is past end of life. This version no longer receives security patches. 89 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 1, 2026
89 days past EOL
Latest Release
gemini-2.0-flash-lite-001
Standard release
Release Date
Feb 25, 2025
Google Gemini gemini-2.0-flash-lite series
Lifecycle detail

Google Gemini gemini-2.0-flash-lite was released on February 25, 2025 and support ended on June 1, 2026 — a supported lifespan of 1 year and 3 months, in line with the 1 year and 4 months median for Google Gemini releases. It has been without security patches for 3 months.

← Google Gemini gemini-2.0-flash All Google Gemini versions Google Gemini gemini-2.5-pro →
55 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
20/30 High tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Google Gemini gemini-3.1-flash-lite
Latest release: gemini-3.1-flash-lite · EOL: May 7, 2027
View full Google Gemini timeline →
All Google Gemini Versions
VersionLatestEOL DateStatus
gemini-1.0-pro-vision gemini-1.0-pro-vision Jul 12, 2024 EOL
gemini-1.0-pro gemini-1.0-pro-002 Apr 9, 2025 EOL
gemini-1.5-flash gemini-1.5-flash-002 Sep 15, 2025 EOL
gemini-1.5-pro gemini-1.5-pro-002 Sep 15, 2025 EOL
text-embedding-004 text-embedding-004 Jan 14, 2026 EOL
gemini-embedding-001 gemini-embedding-001 Jul 14, 2026 EOL
gemini-2.0-flash-lite gemini-2.0-flash-lite-001 Jun 1, 2026 EOL
gemini-2.0-flash gemini-2.0-flash-001 Jun 1, 2026 EOL

What does Google Gemini gemini-2.0-flash-lite end of life mean?

When Google Gemini gemini-2.0-flash-lite reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Google Gemini gemini-2.0-flash-lite past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Google Gemini gemini-3.1-flash-lite or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Google Gemini gemini-2.0-flash-lite reach end of life?
Google Gemini gemini-2.0-flash-lite reached end of life on June 1, 2026. This version is no longer receiving security patches.
Is Google Gemini gemini-2.0-flash-lite still supported?
No. Google Gemini gemini-2.0-flash-lite reached end of life on June 1, 2026 and is no longer receiving security patches.
What should I upgrade to from Google Gemini gemini-2.0-flash-lite?
The recommended upgrade from Google Gemini gemini-2.0-flash-lite is Google Gemini gemini-3.1-flash-lite — the latest actively supported version. Check the Google Gemini full timeline for all supported versions.
What are the security risks of running Google Gemini gemini-2.0-flash-lite past EOL?
When Google Gemini gemini-2.0-flash-lite reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Google Gemini should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →