OpenAI API gpt-3.5-turbo-instruct · Version Status

OpenAI API gpt-3.5-turbo-instruct End of Life Date

OpenAI API gpt-3.5-turbo-instruct end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

OpenAI API gpt-3.5-turbo-instruct reaches end of life on September 28, 2026. Plan your migration now — 30 days remaining.
📅 Get reminded before OpenAI API gpt-3.5-turbo-instruct reaches EOL on September 28, 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
Sep 28, 2026
30 days remaining
Latest Release
gpt-3.5-turbo-instruct
Standard release
Release Date
Sep 18, 2023
OpenAI API gpt-3.5-turbo-instruct series
Lifecycle detail

OpenAI API gpt-3.5-turbo-instruct was released on September 18, 2023 and support is scheduled to end on September 28, 2026 — a planned supported lifespan of 3 years, longer than the 1 year and 6 months median for OpenAI API releases.

← OpenAI API gpt-3.5-turbo-0613 All OpenAI API versions OpenAI API gpt-3.5-turbo-0125 →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
15/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
OpenAI API gpt-4.1-mini
Latest release: gpt-4.1-mini · EOL: Supported
View full OpenAI API timeline →
All OpenAI API Versions
VersionLatestEOL DateStatus
text-davinci-002 text-davinci-002 Jan 4, 2024 EOL
text-davinci-003 text-davinci-003 Jan 4, 2024 EOL
gpt-3.5-turbo-0301 gpt-3.5-turbo-0301 Jun 13, 2023 EOL
gpt-4-0314 gpt-4-0314 Jun 13, 2023 EOL
gpt-3.5-turbo-0613 gpt-3.5-turbo-0613 Sep 13, 2024 EOL
gpt-4-0613 gpt-4-0613 Sep 13, 2024 EOL
gpt-3.5-turbo-instruct gpt-3.5-turbo-instruct Sep 28, 2026 Warning
gpt-3.5-turbo-0125 gpt-3.5-turbo-0125 Oct 23, 2026 Warning

What does OpenAI API gpt-3.5-turbo-instruct end of life mean?

When OpenAI API gpt-3.5-turbo-instruct 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 gpt-3.5-turbo-instruct past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to OpenAI API gpt-4.1-mini or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

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