Complete end-of-life dates, support windows, and security status for all Lua versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.1 | 1.1 | Jul 8, 1994 | Feb 7, 1995 | 11414 days past EOL | EOL |
| 2.1 | 2.1 | Feb 7, 1995 | Nov 28, 1995 | 11120 days past EOL | EOL |
| 2.2 | 2.2 | Nov 28, 1995 | May 14, 1996 | 10952 days past EOL | EOL |
| 2.4 | 2.4 | May 14, 1996 | Nov 19, 1996 | 10763 days past EOL | EOL |
| 2.5 | 2.5.1 | Nov 19, 1996 | Jul 1, 1997 | 10539 days past EOL | EOL |
| 3.0 | 3.0 | Jul 1, 1997 | Jul 11, 1998 | 10164 days past EOL | EOL |
| 3.1 | 3.1 | Jul 11, 1998 | Jul 8, 1999 | 9802 days past EOL | EOL |
| 3.2 | 3.2.2 | Jul 8, 1999 | Feb 22, 2000 | 9573 days past EOL | EOL |
| 4.0 | 4.0.1 | Nov 6, 2000 | Jul 4, 2002 | 8710 days past EOL | EOL |
| 5.0 | 5.0.3 | Apr 11, 2003 | Jun 26, 2006 | 7257 days past EOL | EOL |
| 5.1 | 5.1.5 | Feb 21, 2006 | Feb 17, 2012 | 5195 days past EOL | EOL |
| 5.2 | 5.2.4 | Dec 16, 2011 | Mar 7, 2015 | 4081 days past EOL | EOL |
| 5.3 | 5.3.6 | Jan 12, 2015 | Sep 25, 2020 | 2052 days past EOL | EOL |
| 5.4 | 5.4.8 | Jun 29, 2020 | Already EOL | Supported | Active |
| 5.5 | 5.5.0 | Dec 22, 2025 | Already EOL | Supported | Active |
When a Lua version 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 Lua 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 →