Apache Log4j 2 · Version Status

Apache Log4j 2 End of Life Date

Apache Log4j 2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

✓ Apache Log4j 2 is actively supported. EOL date: TBD.
EOL Date
TBD
Supported
Latest Release
2.26.0
Standard release
Release Date
Jul 12, 2014
Apache Log4j 2 series
← Apache Log4j 1 All Apache Log4j versions Apache Log4j 2.3 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Apache Log4j Versions
VersionLatestEOL DateStatus
1 1.2.17 Oct 15, 2015 EOL
2.3 2.3.2 Sep 20, 2015 EOL
2.12 2.12.4 Dec 14, 2021 EOL
→ 2 2.26.0 EOL Active

What does Apache Log4j 2 end of life mean?

When Apache Log4j 2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Apache Log4j 2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Apache Log4j 2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Apache Log4j 2 reach end of life?
Apache Log4j 2 has already reached end of life.
Is Apache Log4j 2 still supported?
Yes, Apache Log4j 2 is currently supported. The EOL date is TBD.
What should I upgrade to from Apache Log4j 2?
The recommended upgrade from Apache Log4j 2 is Apache Log4j 2 — the latest actively supported version. Check the Apache Log4j full timeline for all supported versions.
What are the security risks of running Apache Log4j 2 past EOL?
When Apache Log4j 2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Apache Log4j should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →