VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

nunjucks: vulnerability history, versions and safety

nunjucks is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 57 releases, from Nov 2018 to Apr 2023. 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 M2
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 nunjucks vulnerabilities

Vulert verdict on nunjucks 3.2.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.2.4 — unaffected i
  • Vulnerabilities on record 2 over 4 years · 0 in the last year i
  • Latest disclosure 20 Apr 2023 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 4,969 packages i
  • Stars 9,003 i
  • OpenSSF scorecard 3/10 i
  • Last release 42 months ago i
  • Licence BSD-2-Clause 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 nunjucks, 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
3.2.4 13 Apr 2023 none BSD-2-Clause — Details →
3.2.3 15 Feb 2021 M1 BSD-2-Clause Yes Details →
3.2.2 20 Jul 2020 M1 BSD-2-Clause Yes Details →
3.2.1 17 Mar 2020 M1 BSD-2-Clause Yes Details →
3.2.0 05 Mar 2019 M1 BSD-2-Clause Yes Details →
3.1.7 12 Jan 2019 M1 BSD-2-Clause Yes Details →
3.1.6 13 Dec 2018 M1 BSD-2-Clause Yes Details →
3.1.4 09 Nov 2018 M1 BSD-2-Clause Yes Details →
3.1.3 19 May 2018 M1 BSD-2-Clause Yes Details →
3.1.2 24 Feb 2018 M1 BSD-2-Clause Yes Details →
3.1.0 20 Feb 2018 M1 BSD-2-Clause Yes Details →
3.0.1 24 May 2017 M1 BSD-2-Clause Yes Details →
3.0.0 05 Nov 2016 M1 BSD-2-Clause Yes Details →
2.5.2 14 Sep 2016 M1 BSD-2-Clause Yes Details →
2.5.1 13 Sep 2016 M1 BSD-2-Clause Yes Details →
2.5.0 07 Sep 2016 M1 BSD-2-Clause Yes Details →
2.4.3 07 Sep 2016 M1 BSD-2-Clause Yes Details →
2.4.2 15 Apr 2016 M2 BSD-2-Clause Yes Details →
2.4.1 17 Mar 2016 M2 BSD-2-Clause Yes Details →
2.4.0 10 Mar 2016 M2 BSD-2-Clause Yes Details →
2.3.0 06 Jan 2016 M2 BSD-2-Clause Yes Details →
2.2.0 23 Nov 2015 M2 BSD-2-Clause Yes Details →
2.1.0 21 Sep 2015 M2 BSD-2-Clause Yes Details →
2.0.0 28 Aug 2015 M2 BSD-2-Clause Yes Details →
1.3.4 27 Apr 2015 M2 non-standard Yes Details →
1.3.3 03 Apr 2015 M2 non-standard Yes Details →
1.3.1 03 Apr 2015 M2 non-standard Yes Details →
1.3.0 03 Apr 2015 M2 non-standard Yes Details →
1.2.0 04 Feb 2015 M2 non-standard Yes Details →
1.1.0 30 Sep 2014 M2 non-standard Yes Details →
1.0.7 15 Aug 2014 M2 non-standard Yes Details →
1.0.6 15 Aug 2014 M2 non-standard Yes Details →
1.0.5 02 May 2014 M2 non-standard Yes Details →
1.0.4 04 Apr 2014 M2 non-standard Yes Details →
1.0.3 04 Apr 2014 M2 non-standard Yes Details →
1.0.2 25 Mar 2014 M2 non-standard Yes Details →
1.0.1 16 Dec 2013 M2 non-standard Yes Details →
0.1.0-a1 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-a2 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-a3 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-a4 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-a5 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-a6 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.0-b1 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.4-a 16 Dec 2013 M2 BSD-2-Clause Yes Details →
0.1.8-a 16 Dec 2013 M2 BSD-2-Clause Yes Details →
1.0.0 24 Oct 2013 M2 BSD-2-Clause Yes Details →
0.1.10 09 Aug 2013 M2 BSD-2-Clause Yes Details →
0.1.9 31 May 2013 M2 BSD-2-Clause Yes Details →
0.1.8 06 Feb 2013 M2 BSD-2-Clause Yes Details →
0.1.7 12 Dec 2012 M2 BSD-2-Clause Yes Details →
0.1.6 13 Nov 2012 M2 BSD-2-Clause Yes Details →
0.1.5 11 Oct 2012 M2 BSD-2-Clause Yes Details →
0.1.4 03 Oct 2012 M2 BSD-2-Clause Yes Details →
0.1.3 01 Oct 2012 M2 BSD-2-Clause Yes Details →
0.1.2 20 Sep 2012 M2 BSD-2-Clause Yes Details →
0.1.1 20 Sep 2012 M2 BSD-2-Clause Yes Details →
0.1.0 19 Sep 2012 M2 BSD-2-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2023 1

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 nunjucks

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-2142: Nunjucks autoescape bypass leads to cross site scripting 6.1 medium 3.2.4 20 Apr 2023
CVE-2016-10547: Cross-Site Scripting in nunjucks N/A medium 2.4.3 06 Nov 2018

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 nunjucks

Is nunjucks safe to use?

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

Vulert scores nunjucks 75/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 nunjucks affected?

No. 3.2.4, 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 nunjucks should I use?

3.2.4 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 nunjucks have?

2 vulnerabilities are recorded for nunjucks in the npm ecosystem: 0 critical, 0 high, 2 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 nunjucks vulnerabilities disclosed?

0 vulnerabilities were recorded for nunjucks in the last 12 months, and the oldest entry in this database dates to 06 Nov 2018. 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 nunjucks 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 nunjucks for upcoming vulnerabilities?

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