Openai API Models GPT-3.5 Turbo · Version Status

Openai API Models GPT-3.5 Turbo End of Life Date

Openai API Models GPT-3.5 Turbo end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

Openai API Models GPT-3.5 Turbo reaches end of life on October 23, 2026. Plan your migration now — 47 days remaining.
📅 Get reminded before Openai API Models GPT-3.5 Turbo reaches EOL on October 23, 2026 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Oct 23, 2026
47 days remaining
Latest Release
Standard release
Release Date
Mar 1, 2023
Openai API Models GPT-3.5 Turbo series
Lifecycle detail

Openai API Models gpt-3.5-turbo was released on March 1, 2023 and support is scheduled to end on October 23, 2026 — a planned supported lifespan of 3 years and 8 months, longer than the 1 year and 5 months median for Openai API Models releases.

← Openai API Models Whisper All Openai API Models versions Openai API Models GPT-4 →
25 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
15/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 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
Openai API Models GPT-6 Astra
Latest release: — · EOL: Supported
View full Openai API Models timeline →
Extended Support
Extended Openai API Models GPT-3.5 Turbo support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Openai API Models Versions
VersionLatestEOL DateStatus
text-embedding-ada-002 EOL Active
text-moderation-stable Oct 27, 2025 EOL
text-moderation Oct 27, 2025 EOL
Whisper Feb 26, 2027 Warning
GPT-3.5 Turbo Oct 23, 2026 Warning
GPT-4 Oct 23, 2026 Warning
davinci-002 Sep 28, 2026 Warning
babbage-002 Sep 28, 2026 Warning

What does Openai API Models GPT-3.5 Turbo end of life mean?

When Openai API Models GPT-3.5 Turbo 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 Openai API Models GPT-3.5 Turbo past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Openai API Models GPT-6 Astra or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Openai API Models GPT-3.5 Turbo reach end of life?
Openai API Models GPT-3.5 Turbo reached end of life on October 23, 2026. That is 47 days remaining.
Is Openai API Models GPT-3.5 Turbo still supported?
Openai API Models GPT-3.5 Turbo is still supported but approaching end of life on October 23, 2026. Begin planning your migration now.
What should I upgrade to from Openai API Models GPT-3.5 Turbo?
The recommended upgrade from Openai API Models GPT-3.5 Turbo is Openai API Models GPT-6 Astra — the latest actively supported version. Check the Openai API Models full timeline for all supported versions.
What are the security risks of running Openai API Models GPT-3.5 Turbo past EOL?
When Openai API Models GPT-3.5 Turbo 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 Openai API Models should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →