log4j end of life dates — full support timeline
3 of 4 tracked log4j releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 2 | 2014-07-12 | not announced | 2.26.0 | supported |
| 2.12 | 2019-06-26 | 2021-12-14 | 2.12.4 | ended |
| 2.3 | 2015-05-10 | 2015-09-20 | 2.3.2 | ended |
| 1 | 2001-01-08 | 2015-10-15 | 1.2.17 | ended |
Who is affected
Anyone running an unsupported log4j release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/log4j, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next log4j deadline
You are reading this because a log4j release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every log4j and related deadline as it is announced, with exact dates and primary sources.
Watch log4j deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.