Apache Log4j 1 · Version Status
Apache Log4j 1 End of Life Date
Apache Log4j 1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Apache Log4j 1 is past end of life. This version no longer receives security patches. 3951 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 15, 2015
3951 days past EOL
Latest Release
1.2.17
Standard release
Release Date
Jan 8, 2001
Apache Log4j 1 series
Lifecycle detail
Apache Log4j 1 was released on January 8, 2001 and support ended on October 15, 2015 — a supported lifespan of 14 years and 9 months, longer than the 2 years and 6 months median for Apache Log4j releases. The last patch it will ever receive is 1.2.17, published May 6, 2012 — 3 years and 5 months before support ended. It has been without security patches for 10 years and 10 months. 1 newer Apache Log4j release has shipped since.
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 →
Extended Support
Extended Apache Log4j 1 support is available
Commercial vendors offer security patches beyond EOL. So far there are 10+ post-EOL CVE fixes documented in vendor release notes. Compare your options.
Compare Options →
All Apache Log4j Versions
| Version | Latest | EOL Date | Status |
|---|
| → 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.1 |
EOL |
Active |
What does Apache Log4j 1 end of life mean?
When Apache Log4j 1 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 1 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 1 reach end of life?
Apache Log4j 1 reached end of life on October 15, 2015. This version is no longer receiving security patches.
Is Apache Log4j 1 still supported?
No. Apache Log4j 1 reached end of life on October 15, 2015 and is no longer receiving security patches.
What should I upgrade to from Apache Log4j 1?
The recommended upgrade from Apache Log4j 1 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 1 past EOL?
When Apache Log4j 1 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.