Apache Log4j — support and end-of-life dates
Apache Log4j 2.12 is the current release, released 2019-06-26, and it reached end of life on 2021-12-14.
- 3 of its 4 tracked cycles have passed their EOL date (earliest tracked cycle 1)
Direct answer
Apache Log4j 2.12 reached end of life on 2021-12-14. Data as of 2026-11-18.
All tracked cycles
| Cycle | Released | Active support ends | End of life (EOL) | Latest | Status |
|---|---|---|---|---|---|
| 2.12 | 2019-06-26 | — | 2021-12-14 1800 days ago | 2.12.4 | End of life |
| 2.3 | 2015-05-10 | — | 2015-09-20 4077 days ago | 2.3.2 | End of life |
| 2 | 2014-07-12 | — | not announced | 2.26.1 | No EOL date |
| 1 | 2001-01-08 | — | 2015-10-15 4052 days ago | 1.2.17 | End of life |
Upgrade path stated in the data
- No successor is stated in the upstream data for this product.
This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.
Questions this page answers
Is Apache Log4j 2.12 end of life?
Yes. Apache Log4j 2.12 reached end of life on 2021-12-14 (1800 days ago).
How many Apache Log4j versions are already end of life?
3 of the 4 cycles tracked here have passed their EOL date as of 2026-11-18.
Other Frameworks & libraries with upcoming deadlines
- Angular — next EOL 2026-11-28 (20)
- Ansible-core — next EOL 2026-11-30 (2.19)
- Ember — next EOL 2026-12-08 (6.8)
- NumPy — next EOL 2026-12-09 (2.2)
- Oracle APEX — next EOL 2026-12-31 (24.1)
- ROS 2 — next EOL 2026-12-31 (kilted)
- Spring Boot — next EOL 2026-12-31 (4.0)
- Spring Security — next EOL 2026-12-31 (7.0)
Source for the cycle table: endoflife.date/log4j
read through the endoflife.date API on 2026-11-18. Machine-readable copy:
/api/eol.json (product key log4j).