OpenAI API gpt-4o-mini · Version Status

OpenAI API gpt-4o-mini End of Life Date

OpenAI API gpt-4o-mini end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

OpenAI API gpt-4o-mini is past end of life. This version no longer receives security patches. 183 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 27, 2026
183 days past EOL
Latest Release
gpt-4o-mini-2024-07-18
Standard release
Release Date
Jul 18, 2024
OpenAI API gpt-4o-mini series
Lifecycle detail

OpenAI API gpt-4o-mini was released on July 18, 2024 and support ended on February 27, 2026 — a supported lifespan of 1 year and 7 months, in line with the 1 year and 6 months median for OpenAI API releases. It has been without security patches for 6 months.

← OpenAI API codex-mini-latest All OpenAI API versions OpenAI API gpt-4o-2024-08-06 →
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
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-4o-mini end of life mean?

When OpenAI API gpt-4o-mini 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-4o-mini 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-4o-mini reach end of life?
OpenAI API gpt-4o-mini reached end of life on February 27, 2026. This version is no longer receiving security patches.
Is OpenAI API gpt-4o-mini still supported?
No. OpenAI API gpt-4o-mini reached end of life on February 27, 2026 and is no longer receiving security patches.
What should I upgrade to from OpenAI API gpt-4o-mini?
The recommended upgrade from OpenAI API gpt-4o-mini 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-4o-mini past EOL?
When OpenAI API gpt-4o-mini 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 →