APACHE LOG4J COVERAGE

Log4j 1.x, 2.3 and 2.12 are end of life. Your patching does not have to be.

Apache Log4j 1.x reached end of life on 5 August 2015, and Log4j 2.3.x and 2.12.x, the last lines for Java 6 and Java 7, have been in end of maintenance since 29 December 2021. OSSeva patches all three after end of life, with Critical fixes within 48 hours. Other versions are assessed case by case.

Who it is forTeams running Log4j 1.x on any Java, or Log4j 2.3 or 2.12 on Java 6 or Java 7, where the runtime or the application cannot move yet
What you getSigned patched builds on the line you run. Assure adds an inventory of every Log4j jar, including copies shaded into other libraries, and an upgrade plan.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your Log4j versions and Java runtime, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Log4j maintenance status by line, read on 19 November 2026

Statuses are from the maintenance table on the Log4j download page. The Log4j project uses end of maintenance for lines where new releases, including security fixes, are very unlikely, and end of life for lines closed by a PMC vote.

LineJavaStatusEnd of maintenance or lifeLast release
Log4j 1.xJava 1.4 and laterEnd of life5 Aug 20151.2.17
Log4j 2.3.xJava 6End of maintenance29 Dec 2021 (endoflife.date lists 20 Sep 2015)2.3.2
Log4j 2.12.xJava 7End of maintenance29 Dec 2021 (endoflife.date lists 14 Dec 2021)2.12.4
Log4j 2.25.x and laterJava 8 and laterMaintainedOnly the newest minor release is in active maintenance2.26.1 (29 Jun 2026)

The download page's table lags the release notes; its own 2.26.x row is marked as in development. The release notes list 2.26.1 on 29 June 2026.

Log4j download page and maintenance table →Log4j versioning and maintenance policy →Log4j release notes →endoflife.date Log4j data →

Log4j advisories that affect the Java 6, Java 7 and 1.x lines

Each row has a published CVE record and an entry on the Log4j security page that agree on the affected range. The first group were fixed in the Java 6 and Java 7 lines. The second group list 2.12.x as affected and are fixed only in 2.25.x, which needs Java 8.

CVEWhat it isAffected rangeFixed in
CVE-2021-44228Log4Shell: JNDI lookup can run code loaded from an LDAP server (CVSS 10.0)2.0-beta9 to before 2.3.1, 2.4 to before 2.12.2, 2.13.0 to before 2.15.02.3.1 (Java 6), 2.12.2 (Java 7), 2.15.0 (Java 8+)
CVE-2021-4104Log4j 1.2 JMSAppender deserialization, when an attacker can write the configurationLog4j 1.2.xNo fix: Log4j 1 is end of life. Safe if no JMSAppender is configured, per the security page
CVE-2025-68161Socket appender does not verify the TLS hostname2.0-beta9 to before 2.25.32.25.3 (Java 8+). No 2.12.x or 2.3.x release
CVE-2026-34477verifyHostName attribute ignored in TLS configuration; the CVE-2025-68161 fix was incomplete2.12.0 to before 2.25.42.25.4 (Java 8+). No 2.12.x release
CVE-2026-34480XmlLayout produces invalid XML and can silently lose log events2.0-alpha1 to before 2.25.42.25.4 (Java 8+). No 2.12.x or 2.3.x release

Log4j 2.3.x and 2.12.x have no release after 29 December 2021, so each entry in the second group is open on 2.12.x, and all but CVE-2026-34477 are open on 2.3.x as well. CVE records and the Log4j security page read on 19 November 2026.

Log4j security page →CVE-2021-44228 record →CVE-2025-68161 record →

Staying on Java 7 means staying on Log4j 2.12.4 or older

The Log4j release notes say Java 6 and Java 7 are no longer supported by the Log4j team, and the installation page puts the minimum for Log4j 2 at Java 8. That makes the logging library, not only the JDK, part of any Java 7 retirement plan.

  • Fixes stop at the last Java 7 release. Log4Shell was fixed in 2.12.2 and the later 2021 advisories in 2.12.3, per the security page, but the three advisories above were published from December 2025 and have no 2.12.x fix.
  • Log4j API and Log4j Core must be aligned. The versioning policy says Core version X depends on API version X, so replacing only log4j-core on a Java 7 estate does not work: the 2.25 jars will not load on a Java 7 runtime.
  • Look for shaded copies. Applications and vendor products often bundle Log4j inside another jar, so a dependency tree of the application can be clean while a scanner finds log4j-core in a fat jar. Inventory by jar contents, not by build files.
  • Check the configuration before ranking. CVE-2025-68161 and CVE-2026-34477 matter only if the Socket appender is used with TLS and the hostname check is expected. CVE-2026-34480 matters only if XmlLayout is configured. Log4j 1 findings other than the JMSAppender one are not published on the Log4j security page.
  • Plan the move as two steps. First Java 8 or later, then Log4j 2.25 or later, using the log4j-bom artifact so the API and Core versions stay aligned. OSSeva keeps the 2.12 or 2.3 line patched in between.

Sources: the Log4j security page, installation page, release notes, versioning policy and download page, read on 19 November 2026.

Log4j installation requirements →Apache Struts support →Apache Tomcat support →Log4Shell two years later →

Why now

Log4j 1.x ended in August 2015

The Log4j security page says Log4j 1 reached end of life in 2015 and that vulnerabilities reported after August 2015 are not checked and will not be fixed. The last release was 1.2.17. Log4j 1 has no lookups, but CVE-2021-4104 applies to a JMSAppender configuration.

Java 6 and Java 7 stopped at 2.3.2 and 2.12.4

Log4j 2.12.4 is the last release for Java 7 and 2.3.2 the last for Java 6. Both lines went to end of maintenance on 29 December 2021. The Log4j 2 runtime now needs Java 8, so every fix since then is on a line a Java 7 application cannot run.

Newer advisories name 2.12.x and fix it only in 2.25

CVE-2025-68161 and CVE-2026-34477 list Log4j 2.12.x as affected, and the Log4j security page shows the fix only in 2.25.3 and 2.25.4. CVE-2021-44228, the Log4Shell flaw, was fixed for these lines in 2.3.1 and 2.12.2, so a Java 7 estate that patched Log4Shell in 2021 has no fix for these later advisories.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
1.x(End of life 5 Aug 2015)EOLSee advisories
2.3.x(Last Java 6 line, end of maintenance 29 Dec 2021)EOLSee advisories
2.12.x(Last Java 7 line, end of maintenance 29 Dec 2021)EOLSee advisories
2.25.x and later(Maintained by the Log4j project. Assessed case by case.)CurrentSee advisories

Running a Apache Log4j version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for Log4j 1.x, 2.3.x and 2.12.x.

  • Backported security fixes for Log4j 1.x, 2.3.x and 2.12.x
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and a logging upgrade plan.

  • Everything in Patch
  • Inventory of every Log4j jar, including shaded copies
  • Java 7 to Java 8 and Log4j 2.25 upgrade path assessment
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Is Log4j 1.x end of life?

Yes. The Log4j project says Log4j 1 reached end of life in 2015, and its maintenance table gives 5 August 2015. Vulnerabilities reported after August 2015 are not checked and will not be fixed. The last release was 1.2.17.

Which Log4j versions does OSSeva patch?

Log4j 1.x, 2.3.x and 2.12.x after end of life. Other versions are assessed case by case through a version coverage check.

Is Log4j 2.12 end of life?

The Log4j project lists 2.12.x as end of maintenance since 29 December 2021, with 2.12.4 as the last release and the last one that supports Java 7. At that stage new releases, including security fixes, are described as very unlikely. endoflife.date records 14 December 2021 as the end date.

Does Log4j 2.12.4 have known vulnerabilities?

Yes. The Log4j security page and the CVE records list CVE-2025-68161 (Socket appender TLS hostname verification), CVE-2026-34477 (the verifyHostName setting ignored) and CVE-2026-34480 (XmlLayout) against 2.12.x. Each is fixed only in 2.25.3 or 2.25.4, which need Java 8 or later.

Was Log4Shell fixed in Log4j 2.12 and 2.3?

Yes. CVE-2021-44228 was fixed in 2.3.1 for Java 6, 2.12.2 for Java 7 and 2.15.0 for Java 8 and later, per the Log4j security page. The final releases, 2.3.2 and 2.12.4, include those fixes. Later advisories are the open question for those lines.

Does Log4j 2 run on Java 7?

Not any current release. The Log4j installation page says the Log4j 2 runtime requires Java 8 as a minimum, and the release notes say Log4j 2.12.4 is the last release to support Java 7 and 2.3.2 the last for Java 6.

How fast are Log4j vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

How is OSSeva Log4j support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get Apache Log4j patched and supported?

Tell us your Apache Log4j versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call