VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

log4j:log4j: vulnerability history, versions and safety

log4j:log4j is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 14 releases, from Jan 2020 to Jan 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C3 H2
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all log4j:log4j vulnerabilities

Vulert verdict on log4j:log4j 1.2.17 i

Updated on 23 Oct 2026

Careful: 1.2.17 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.2.17 — affected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 21 Jan 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Depended on by 30,876 packages i
  • Last release 172 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for log4j:log4j, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.2.17 26 May 2012 C3 H2 Apache-2.0 No Details →
1.2.16 31 Mar 2010 C3 H2 Apache-2.0 No Details →
1.2.15 30 Aug 2007 C3 H2 Apache-2.0 No Details →
1.2.14 01 Dec 2006 C3 H2 Apache-2.0 No Details →
1.2.13 03 Jan 2006 C3 H2 — No Details →
1.2.7 22 Nov 2005 C3 H2 — No Details →
1.2.8 22 Nov 2005 C3 H2 — No Details →
1.2.9 22 Nov 2005 C3 H2 — No Details →
1.2.12 22 Nov 2005 C3 H2 — No Details →
1.2.4 22 Nov 2005 C3 H2 — No Details →
1.2.5 22 Nov 2005 C3 H2 — No Details →
1.2.6 22 Nov 2005 C3 H2 — No Details →
1.1.3 22 Nov 2005 C2 H1 — No Details →
1.2.11 22 Nov 2005 C3 H2 — No Details →

All 14 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2022 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for log4j:log4j

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17571: Log4j Deserialization of Untrusted Data 9.8 critical No fix published 06 Jan 2020
CVE-2022-23305: SQL Injection in Log4j 1.2.x 9.8 critical No fix published 21 Jan 2022
CVE-2022-23307: Apache Log4j Deserialization of Untrusted Data 9.8 critical No fix published 19 Jan 2022
CVE-2022-23302: Log4j 1.x Deserialization of Untrusted Data 8.8 high No fix published 21 Jan 2022
CVE-2021-4104: Log4j 1.2 JMSAppender Deserialization Vulnerability 7.5 high No fix published 14 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About log4j:log4j

Is log4j:log4j safe to use?

Vulert records 5 vulnerabilities for log4j:log4j in Maven: 3 critical, 2 high, 0 medium and 0 low. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is log4j:log4j's Vulert package health score?

Vulert scores log4j:log4j 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of log4j:log4j affected?

Yes. 1.2.17, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does log4j:log4j have?

5 vulnerabilities are recorded for log4j:log4j in the Maven ecosystem: 3 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new log4j:log4j vulnerabilities disclosed?

0 vulnerabilities were recorded for log4j:log4j in the last 12 months, and the oldest entry in this database dates to 06 Jan 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of log4j:log4j are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor log4j:log4j for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the log4j:log4j version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.