VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

log4js: vulnerability history, versions and safety

log4js is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 102 releases, first recorded in 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
1 vulnerabilities recorded M1
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 log4js vulnerabilities

Vulert verdict on log4js 6.9.1 i

Updated on 23 Oct 2026

Good news: 6.9.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 77/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 6.9.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Jan 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Depended on by 5,497 packages i
  • Stars 5,823 i
  • OpenSSF scorecard 4/10 i
  • Last release 43 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 log4js, 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
6.9.1 08 Mar 2023 none Apache-2.0 — Details →
6.9.0 07 Mar 2023 none Apache-2.0 — Details →
6.8.0 20 Feb 2023 none Apache-2.0 — Details →
6.7.1 28 Nov 2022 none Apache-2.0 — Details →
6.7.0 01 Oct 2022 none Apache-2.0 — Details →
6.6.1 26 Jul 2022 none Apache-2.0 — Details →
6.6.0 06 Jul 2022 none Apache-2.0 — Details →
6.5.2 27 May 2022 none Apache-2.0 — Details →
6.5.1 23 May 2022 none Apache-2.0 — Details →
6.5.0 22 May 2022 none Apache-2.0 — Details →
6.4.7 14 May 2022 none Apache-2.0 — Details →
6.4.6 25 Apr 2022 none Apache-2.0 — Details →
6.4.5 15 Apr 2022 none Apache-2.0 — Details →
6.4.4 22 Mar 2022 none Apache-2.0 — Details →
6.4.3 15 Mar 2022 none Apache-2.0 — Details →
6.4.2 02 Mar 2022 none Apache-2.0 — Details →
6.4.1 23 Jan 2022 none Apache-2.0 — Details →
6.4.0 19 Jan 2022 none Apache-2.0 — Details →
6.3.0 24 May 2020 M1 Apache-2.0 Yes Details →
6.2.1 19 Apr 2020 M1 Apache-2.0 Yes Details →
6.2.0 14 Apr 2020 M1 Apache-2.0 Yes Details →
6.1.2 10 Feb 2020 M1 Apache-2.0 Yes Details →
6.1.1 29 Jan 2020 M1 Apache-2.0 Yes Details →
6.1.0 19 Nov 2019 M1 Apache-2.0 Yes Details →
6.0.0 12 Nov 2019 M1 Apache-2.0 Yes Details →
5.3.0 22 Oct 2019 M1 Apache-2.0 Yes Details →
5.2.2 10 Oct 2019 M1 Apache-2.0 Yes Details →
5.2.1 08 Oct 2019 M1 Apache-2.0 Yes Details →
5.2.0 04 Oct 2019 M1 Apache-2.0 Yes Details →
5.1.0 22 Aug 2019 M1 Apache-2.0 Yes Details →
5.0.0 11 Aug 2019 M1 Apache-2.0 Yes Details →
4.5.1 12 Jul 2019 M1 Apache-2.0 Yes Details →
4.5.0 09 Jul 2019 M1 Apache-2.0 Yes Details →
4.4.0 25 Jun 2019 M1 Apache-2.0 Yes Details →
4.3.2 19 Jun 2019 M1 Apache-2.0 Yes Details →
4.3.1 28 May 2019 M1 Apache-2.0 Yes Details →
4.3.0 22 May 2019 M1 Apache-2.0 Yes Details →
4.2.0 14 May 2019 M1 Apache-2.0 Yes Details →
4.1.1 06 May 2019 M1 Apache-2.0 Yes Details →
4.1.0 25 Mar 2019 M1 Apache-2.0 Yes Details →
4.0.2 03 Feb 2019 M1 Apache-2.0 Yes Details →
4.0.1 28 Jan 2019 M1 Apache-2.0 Yes Details →
4.0.0 24 Jan 2019 M1 Apache-2.0 Yes Details →
3.0.6 08 Oct 2018 M1 Apache-2.0 Yes Details →
3.0.5 12 Aug 2018 M1 Apache-2.0 Yes Details →
3.0.4 01 Aug 2018 M1 Apache-2.0 Yes Details →
3.0.3 29 Jul 2018 M1 Apache-2.0 Yes Details →
3.0.2 20 Jul 2018 M1 Apache-2.0 Yes Details →
3.0.1 19 Jul 2018 M1 Apache-2.0 Yes Details →
3.0.0 15 Jul 2018 M1 Apache-2.0 Yes Details →
2.11.0 12 Jul 2018 M1 Apache-2.0 Yes Details →
2.10.0 24 Jun 2018 M1 Apache-2.0 Yes Details →
2.9.0 14 Jun 2018 M1 Apache-2.0 Yes Details →
2.8.0 30 May 2018 M1 Apache-2.0 Yes Details →
2.7.0 20 May 2018 M1 Apache-2.0 Yes Details →
2.6.1 15 May 2018 M1 Apache-2.0 Yes Details →
2.6.0 11 May 2018 M1 Apache-2.0 Yes Details →
2.5.3 11 Feb 2018 M1 Apache-2.0 Yes Details →
2.5.2 18 Jan 2018 M1 Apache-2.0 Yes Details →
2.5.1 17 Jan 2018 M1 Apache-2.0 Yes Details →
2.5.0 17 Jan 2018 M1 Apache-2.0 Yes Details →
2.4.1 11 Dec 2017 M1 Apache-2.0 Yes Details →
2.3.12 13 Nov 2017 M1 Apache-2.0 Yes Details →
2.3.11 01 Nov 2017 M1 Apache-2.0 Yes Details →
2.3.10 25 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.9 24 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.8 23 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.7 16 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.6 16 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.5 11 Oct 2017 M1 Apache-2.0 Yes Details →
2.3.4 25 Sep 2017 M1 Apache-2.0 Yes Details →
2.3.3 02 Aug 2017 M1 Apache-2.0 Yes Details →
2.3.2 27 Jul 2017 M1 Apache-2.0 Yes Details →
2.3.1 26 Jul 2017 M1 Apache-2.0 Yes Details →
2.3.0 23 Jul 2017 M1 Apache-2.0 Yes Details →
2.2.0 16 Jul 2017 M1 Apache-2.0 Yes Details →
2.1.0 13 Jul 2017 M1 Apache-2.0 Yes Details →
2.0.1 10 Jul 2017 M1 Apache-2.0 Yes Details →
2.0.0 08 Jul 2017 M1 Apache-2.0 Yes Details →
1.1.1 02 Mar 2017 M1 Apache-2.0 Yes Details →
1.1.0 20 Dec 2016 M1 Apache-2.0 Yes Details →
1.0.1 06 Nov 2016 M1 Apache-2.0 Yes Details →
1.0.0 03 Nov 2016 M1 Apache-2.0 Yes Details →
0.6.38 17 Jul 2016 M1 Apache-2.0 Yes Details →
0.6.37 14 Jun 2016 M1 Apache-2.0 Yes Details →
0.6.36 05 May 2016 M1 Apache-2.0 Yes Details →
0.6.35 14 Apr 2016 M1 Apache-2.0 Yes Details →
0.6.34 14 Apr 2016 M1 Apache-2.0 Yes Details →
0.6.33 08 Mar 2016 M1 Apache-2.0 Yes Details →
0.6.32 28 Feb 2016 M1 Apache-2.0 Yes Details →
0.6.31 01 Feb 2016 M1 Apache-2.0 Yes Details →
0.6.30 26 Jan 2016 M1 Apache-2.0 Yes Details →
0.6.29 26 Nov 2015 M1 Apache-2.0 Yes Details →
0.6.28 18 Nov 2015 M1 Apache-2.0 Yes Details →
0.6.27 21 Sep 2015 M1 Apache-2.0 Yes Details →
0.6.26 10 Jun 2015 M1 Apache-2.0 Yes Details →
0.6.25 12 May 2015 M1 Apache-2.0 Yes Details →
0.6.24 17 Apr 2015 M1 Apache-2.0 Yes Details →
0.6.23 16 Apr 2015 M1 Apache-2.0 Yes Details →
0.6.22 10 Jan 2015 M1 Apache-2.0 Yes Details →
0.6.21 10 Sep 2014 M1 — Yes Details →
0.6.20 25 Aug 2014 M1 — Yes Details →
0.6.19 21 Aug 2014 M1 — Yes Details →
0.6.18 19 Aug 2014 M1 — Yes Details →
0.6.17 15 Aug 2014 M1 — Yes Details →
0.6.16 18 Jul 2014 M1 — Yes Details →
0.6.15 02 Jul 2014 M1 — Yes Details →
0.6.14 22 Apr 2014 M1 — Yes Details →
0.6.13 08 Apr 2014 M1 — Yes Details →
0.6.12 05 Mar 2014 M1 — Yes Details →
0.6.11 04 Mar 2014 M1 — Yes Details →
0.6.10 10 Feb 2014 M1 — Yes Details →
0.6.9 29 Sep 2013 M1 — Yes Details →
0.6.8 22 Aug 2013 M1 — Yes Details →
0.6.7 02 Aug 2013 M1 — Yes Details →
0.6.6 25 May 2013 M1 — Yes Details →
0.6.5 16 May 2013 M1 — Yes Details →
0.6.4 05 May 2013 M1 — Yes Details →
0.6.3 11 Apr 2013 M1 — Yes Details →
0.6.2 02 Apr 2013 M1 — Yes Details →

The newest 120 of 152 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for log4js

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-21704: Incorrect Default Permissions in log4js 5.5 medium 6.4.0 21 Jan 2022

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 log4js

Is log4js safe to use?

Vulert records 1 vulnerabilities for log4js in npm: 0 critical, 0 high, 1 medium and 0 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 log4js's Vulert package health score?

Vulert scores log4js 77/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 log4js affected?

No. 6.9.1, 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 log4js should I use?

6.9.1 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 log4js have?

1 vulnerability is recorded for log4js in the npm ecosystem: 0 critical, 0 high, 1 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 log4js vulnerabilities disclosed?

0 vulnerabilities were recorded for log4js in the last 12 months, and the oldest entry in this database dates to 21 Jan 2022. 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 log4js 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 log4js for upcoming vulnerabilities?

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