← ← Back to all products
Apache Log4j
Active
Libraries & SDKsLatest Version: 2.26.0Latest Release: May 2, 2026
Apache Log4j is a Java-based logging framework widely used for application logging and diagnostics.
Support summary
Apache Log4j currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
4
Latest Version
2.26.0
Active Support
1
EOL
3
Lifecycle Timeline
Today ↓
2
2
2.12
2.12
2.3
2.3
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2 | Jul 12, 2014 | Yes | No | 2.26.0 | No | Active |
| 2.12 | Jun 26, 2019 | No | Dec 14, 2021 | 2.12.4 | No | EOL |
| 2.3 | May 10, 2015 | No | Sep 20, 2015 | 2.3.2 | No | EOL |
| 1 | Jan 8, 2001 | No | Oct 15, 2015 | 1.2.17 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Apache Log4j have reached end of life?
The following Apache Log4j versions have reached end of life and no longer receive security updates: 2.12, 2.3, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Log4j 2.12?
Apache Log4j 2.12 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache Log4j?
The latest version of Apache Log4j is 2.26.0, released in the 2 release cycle.
How many versions of Apache Log4j are currently supported?
Apache Log4j currently has 1 actively supported version(s): 2.
When does Apache Log4j 2 reach end of life?
Apache Log4j 2 does not have a specific end-of-life date announced yet.
What should I do when Apache Log4j reaches end of life?
When a Apache Log4j version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.