OpenAI API codex-mini-latest End of Life Date
OpenAI API codex-mini-latest end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
OpenAI API codex-mini-latest was released on June 1, 2024 and support ended on February 12, 2026 — a supported lifespan of 1 year and 9 months, in line with the 1 year and 6 months median for OpenAI API releases. It has been without security patches for 7 months.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 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 codex-mini-latest end of life mean?
When OpenAI API codex-mini-latest 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 codex-mini-latest 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.