Google Gemini text-embedding-004 · Version Status

Google Gemini text-embedding-004 End of Life Date

Google Gemini text-embedding-004 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Google Gemini text-embedding-004 is past end of life. This version no longer receives security patches. 227 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 14, 2026
227 days past EOL
Latest Release
text-embedding-004
Standard release
Release Date
Apr 9, 2024
Google Gemini text-embedding-004 series
Lifecycle detail

Google Gemini text-embedding-004 was released on April 9, 2024 and support ended on January 14, 2026 — a supported lifespan of 1 year and 9 months, longer than the 1 year and 4 months median for Google Gemini releases. It has been without security patches for 8 months. 1 newer Google Gemini release has shipped since.

← Google Gemini gemini-1.0-pro-vision All Google Gemini versions Google Gemini gemini-1.5-pro →
60 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/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 text-embedding-004 end of life mean?

When Google Gemini text-embedding-004 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 text-embedding-004 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 text-embedding-004 reach end of life?
Google Gemini text-embedding-004 reached end of life on January 14, 2026. This version is no longer receiving security patches.
Is Google Gemini text-embedding-004 still supported?
No. Google Gemini text-embedding-004 reached end of life on January 14, 2026 and is no longer receiving security patches.
What should I upgrade to from Google Gemini text-embedding-004?
The recommended upgrade from Google Gemini text-embedding-004 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 text-embedding-004 past EOL?
When Google Gemini text-embedding-004 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 →