Meta Llama End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Meta Llama versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| llama-2-7b | llama-2-7b-chat | Jul 18, 2023 | Jul 23, 2024 | 722 days past EOL | EOL |
| llama-2-13b | llama-2-13b-chat | Jul 18, 2023 | Jul 23, 2024 | 722 days past EOL | EOL |
| llama-2-70b | llama-2-70b-chat | Jul 18, 2023 | Jul 23, 2024 | 722 days past EOL | EOL |
| llama-3-8b | llama-3-8b-instruct | Apr 18, 2024 | May 31, 2025 | 410 days past EOL | EOL |
| llama-3-70b | llama-3-70b-instruct | Apr 18, 2024 | May 31, 2025 | 410 days past EOL | EOL |
| llama-3.1-8b | llama-3.1-8b-instruct | Jul 23, 2024 | No EOL date | Supported | Active |
| llama-3.1-70b | llama-3.1-70b-instruct | Jul 23, 2024 | Jan 24, 2025 | 537 days past EOL | EOL |
| llama-3.1-405b | llama-3.1-405b-instruct | Jul 23, 2024 | No EOL date | Supported | Active |
| llama-3.2-1b | llama-3.2-1b-instruct | Sep 25, 2024 | No EOL date | Supported | Active |
| llama-3.2-3b | llama-3.2-3b-instruct | Sep 25, 2024 | No EOL date | Supported | Active |
| llama-3.2-11b | llama-3.2-11b-vision-instruct | Sep 25, 2024 | No EOL date | Supported | Active |
| llama-3.2-90b | llama-3.2-90b-vision-instruct | Sep 25, 2024 | No EOL date | Supported | Active |
| llama-3.3-70b | llama-3.3-70b-instruct | Dec 6, 2024 | No EOL date | Supported | Active |
| llama-4-scout | llama-4-scout | Apr 5, 2025 | No EOL date | Supported | Active |
| llama-4-maverick | llama-4-maverick | Apr 5, 2025 | No EOL date | Supported | Active |
What does Meta Llama end of life mean for your organization?
When a version of Meta Llama reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Meta Llama should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →