OpenAI API gpt-4-turbo · Version Status

OpenAI API gpt-4-turbo End of Life Date

OpenAI API gpt-4-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 gpt-4-turbo reaches end of life on October 23, 2026. Plan your migration now — 10 days remaining.
📅 Get reminded before OpenAI API gpt-4-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
10 days remaining
Latest Release
gpt-4-turbo-2024-04-09
Standard release
Release Date
Apr 9, 2024
OpenAI API gpt-4-turbo series
Lifecycle detail

OpenAI API gpt-4-turbo was released on April 9, 2024 and support is scheduled to end on October 23, 2026 — a planned supported lifespan of 2 years and 7 months, longer than the 1 year and 6 months median for OpenAI API releases.

← OpenAI API gpt-3.5-turbo-0125 All OpenAI API versions OpenAI API gpt-4o-2024-05-13 →
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 Oct 23, 2026 Warning
gpt-3.5-turbo-instruct gpt-3.5-turbo-instruct Sep 28, 2026 EOL
gpt-3.5-turbo-0125 gpt-3.5-turbo-0125 Oct 23, 2026 Warning

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

When OpenAI API gpt-4-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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running OpenAI API gpt-4-turbo past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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-4-turbo reach end of life?
OpenAI API gpt-4-turbo reaches end of life on October 23, 2026. That is 10 days remaining.
Is OpenAI API gpt-4-turbo still supported?
OpenAI API gpt-4-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 gpt-4-turbo?
The recommended upgrade from OpenAI API gpt-4-turbo 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-4-turbo past EOL?
When OpenAI API gpt-4-turbo reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. 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 →