VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.logging.log4j:log4j: vulnerability history, versions and safety

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

i
2 vulnerabilities recorded C1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 org.apache.logging.log4j:log4j vulnerabilities

Vulert verdict on org.apache.logging.log4j:log4j 3.0.0-beta3 i

Updated on 23 Oct 2026

Good news: 3.0.0-beta3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 78/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Active

What to do: Stay on 3.0.0-beta3 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.0.0-beta3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.0.0-beta3 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Jun 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 85 packages i
  • Stars 3,639 i
  • OpenSSF scorecard 7/10 i
  • Last release 23 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 org.apache.logging.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
2.25.5 01 Jul 2026 none Apache-2.0 — Details →
2.26.1 29 Jun 2026 none Apache-2.0 — Details →
2.26.0 02 May 2026 none Apache-2.0 — Details →
2.25.4 25 Mar 2026 none Apache-2.0 — Details →
2.25.3 15 Dec 2025 none Apache-2.0 — Details →
2.25.2 18 Sep 2025 none Apache-2.0 — Details →
2.25.1 05 Jul 2025 none Apache-2.0 — Details →
2.25.0 13 Jun 2025 none Apache-2.0 — Details →
2.24.3 10 Dec 2024 none Apache-2.0 — Details →
2.24.2 18 Nov 2024 none Apache-2.0 — Details →
3.0.0-beta3 09 Nov 2024 none Apache-2.0 — Details →
2.24.1 24 Sep 2024 none Apache-2.0 — Details →
2.24.0 03 Sep 2024 none Apache-2.0 — Details →
2.23.1 06 Mar 2024 none Apache-2.0 — Details →
3.0.0-beta2 17 Feb 2024 none Apache-2.0 — Details →
2.23.0 17 Feb 2024 none Apache-2.0 — Details →
2.22.1 22 Dec 2023 none Apache-2.0 — Details →
3.0.0-beta1 19 Dec 2023 none Apache-2.0 — Details →
2.22.0 17 Nov 2023 none Apache-2.0 — Details →
2.21.1 20 Oct 2023 none Apache-2.0 — Details →
2.21.0 12 Oct 2023 none Apache-2.0 — Details →
3.0.0-alpha1 18 Jun 2023 none Apache-2.0 — Details →
2.20.0 18 Feb 2023 none Apache-2.0 — Details →
2.19.0 13 Sep 2022 none Apache-2.0 — Details →
2.18.0 28 Jun 2022 none Apache-2.0 — Details →
2.17.2 23 Feb 2022 none Apache-2.0 — Details →
2.3.2 29 Dec 2021 C1 Apache-2.0 Yes Details →
2.12.4 28 Dec 2021 none Apache-2.0 — Details →
2.17.1 27 Dec 2021 none Apache-2.0 — Details →
2.3.1 21 Dec 2021 C1 Apache-2.0 Yes Details →
2.12.3 20 Dec 2021 none Apache-2.0 — Details →
2.17.0 18 Dec 2021 none Apache-2.0 — Details →
2.12.2 14 Dec 2021 none Apache-2.0 — Details →
2.16.0 13 Dec 2021 none Apache-2.0 — Details →
2.15.0 09 Dec 2021 none Apache-2.0 — Details →
2.14.1 07 Mar 2021 none Apache-2.0 — Details →
2.14.0 06 Nov 2020 none Apache-2.0 — Details →
2.13.3 10 May 2020 none Apache-2.0 — Details →
2.13.2 21 Apr 2020 none Apache-2.0 — Details →
2.13.1 26 Feb 2020 L1 Apache-2.0 Yes Details →
2.13.0 12 Dec 2019 L1 Apache-2.0 Yes Details →
2.12.1 07 Aug 2019 none Apache-2.0 — Details →
2.12.0 26 Jun 2019 none Apache-2.0 — Details →
2.11.2 06 Feb 2019 none Apache-2.0 — Details →
2.11.1 23 Jul 2018 none Apache-2.0 — Details →
2.11.0 11 Mar 2018 none Apache-2.0 — Details →
2.10.0 19 Nov 2017 none Apache-2.0 — Details →
2.9.1 18 Sep 2017 none Apache-2.0 — Details →
2.9.0 26 Aug 2017 none Apache-2.0 — Details →
2.8.2 02 Apr 2017 none Apache-2.0 — Details →
2.8.1 26 Feb 2017 C1 Apache-2.0 Yes Details →
2.8 22 Jan 2017 C1 Apache-2.0 Yes Details →
2.7 02 Oct 2016 C1 Apache-2.0 Yes Details →
2.6.2 06 Jul 2016 C1 Apache-2.0 Yes Details →
2.6.1 06 Jun 2016 C1 Apache-2.0 Yes Details →
2.6 25 May 2016 C1 Apache-2.0 Yes Details →
2.5 07 Dec 2015 C1 Apache-2.0 Yes Details →
2.4.1 09 Oct 2015 C1 Apache-2.0 Yes Details →
2.4 20 Sep 2015 C1 Apache-2.0 Yes Details →
2.3 10 May 2015 C1 Apache-2.0 Yes Details →
2.2 22 Feb 2015 C1 Apache-2.0 Yes Details →
2.1 20 Oct 2014 C1 Apache-2.0 Yes Details →
2.0.2 17 Aug 2014 C1 Apache-2.0 Yes Details →
2.0.1 30 Jul 2014 C1 Apache-2.0 Yes Details →
2.0 12 Jul 2014 C1 Apache-2.0 Yes Details →
2.0-rc2 21 Jun 2014 none Apache-2.0 — Details →
2.0-rc1 09 Feb 2014 none Apache-2.0 — Details →
2.0-beta9 14 Sep 2013 none Apache-2.0 — Details →
2.0-beta8 10 Jul 2013 none Apache-2.0 — Details →
2.0-beta7 04 Jun 2013 none Apache-2.0 — Details →
2.0-beta6 07 May 2013 none Apache-2.0 — Details →
2.0-beta5 20 Apr 2013 none Apache-2.0 — Details →
2.0-beta4 28 Jan 2013 none Apache-2.0 — Details →
2.0-beta3 11 Nov 2012 none Apache-2.0 — Details →
2.0-beta2 07 Oct 2012 none Apache-2.0 — Details →
2.0-beta1 18 Sep 2012 none Apache-2.0 — Details →
2.0-alpha2 24 Aug 2012 none Apache-2.0 — Details →
2.0-alpha1 29 Jul 2012 none Apache-2.0 — Details →

All 78 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.logging.log4j:log4j

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-5645: Deserialization of Untrusted Data in Log4j 9.8 critical 2.8.2 06 Jan 2020
CVE-2020-9488: Improper validation of certificate with host mismatch in Apache Log4j SMTP appender 3.7 low 2.13.2 05 Jun 2020

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 org.apache.logging.log4j:log4j

Is org.apache.logging.log4j:log4j safe to use?

Vulert records 2 vulnerabilities for org.apache.logging.log4j:log4j in Maven: 1 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.logging.log4j:log4j's Vulert package health score?

Vulert scores org.apache.logging.log4j:log4j 78/100, which reads as in good shape. 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).

Is the latest version of org.apache.logging.log4j:log4j affected?

No. 3.0.0-beta3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.logging.log4j:log4j should I use?

3.0.0-beta3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.logging.log4j:log4j have?

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

How often are new org.apache.logging.log4j:log4j vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.logging.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 org.apache.logging.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 org.apache.logging.log4j:log4j for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.logging.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.