Apache Log4j End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Log4j 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.2.17 | Jan 8, 2001 | Oct 15, 2015 | 3904 days past EOL | EOL |
| 2.3 | 2.3.2 | May 10, 2015 | Sep 20, 2015 | 3929 days past EOL | EOL |
| 2.12 | 2.12.4 | Jun 26, 2019 | Dec 14, 2021 | 1652 days past EOL | EOL |
| 2 | 2.26.0 | Jul 12, 2014 | TBD | Supported | Active |
What does Apache Log4j end of life mean for your organization?
When a version of Apache Log4j 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 Apache Log4j 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Apache Log4j versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →