VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

handlebars: vulnerability history, versions and safety

handlebars is a package in the npm ecosystem. Vulert records 25 vulnerabilities for it across 81 releases, from Oct 2017 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded C7 H10 M7 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
11 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all handlebars vulnerabilities

Vulert verdict on handlebars 4.7.10 i

Updated on 22 Oct 2026

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

Package health score 64/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.7.10 — unaffected i
  • Vulnerabilities on record 25 over 8 years · 11 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 56,564 packages i
  • Stars 18,688 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 handlebars, 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
4.7.10 05 Oct 2026 none MIT — Details →
4.7.9 26 Mar 2026 C2 M1 MIT Yes Details →
4.7.8 01 Aug 2023 C3 H4 M3 L1 MIT Yes Details →
4.7.7 15 Feb 2021 C3 H4 M3 L1 MIT Yes Details →
4.7.6 03 Apr 2020 C6 H4 M3 L1 MIT Yes Details →
4.7.5 02 Apr 2020 C6 H4 M3 L1 MIT Yes Details →
4.7.4 01 Apr 2020 C6 H4 M3 L1 MIT Yes Details →
3.0.8 23 Feb 2020 C3 M3 MIT Yes Details →
4.7.3 05 Feb 2020 C6 H4 M3 L1 MIT Yes Details →
4.7.2 13 Jan 2020 C6 H4 M3 L1 MIT Yes Details →
4.7.1 12 Jan 2020 C6 H4 M3 L1 MIT Yes Details →
4.7.0 10 Jan 2020 C6 H4 M3 L1 MIT Yes Details →
4.6.0 08 Jan 2020 C6 H4 M3 L1 MIT Yes Details →
4.5.3 18 Nov 2019 C6 H4 M2 L1 MIT Yes Details →
4.5.2 13 Nov 2019 C6 H4 M2 L1 MIT Yes Details →
4.5.1 29 Oct 2019 C6 H4 M2 L1 MIT Yes Details →
4.5.0 28 Oct 2019 C6 H4 M2 L1 MIT Yes Details →
4.4.5 20 Oct 2019 C6 H4 M2 L1 MIT Yes Details →
4.4.4 20 Oct 2019 C6 H5 M3 L1 MIT Yes Details →
4.4.3 08 Oct 2019 C6 H5 M3 L1 MIT Yes Details →
4.4.2 02 Oct 2019 C6 H5 M3 L1 MIT Yes Details →
4.2.2 02 Oct 2019 C7 H5 M3 L1 MIT Yes Details →
4.3.5 02 Oct 2019 C6 H5 M3 L1 MIT Yes Details →
4.4.1 02 Oct 2019 C6 H5 M3 L1 MIT Yes Details →
4.4.0 29 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.3.4 28 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.3.3 27 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.3.2 26 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.3.1 24 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.3.0 24 Sep 2019 C6 H5 M3 L1 MIT Yes Details →
4.2.1 20 Sep 2019 C7 H5 M3 L1 MIT Yes Details →
4.2.0 03 Sep 2019 C7 H5 M3 L1 MIT Yes Details →
4.1.2-0 25 Aug 2019 C7 H5 M3 L1 MIT Yes Details →
3.0.7 30 Jun 2019 C3 H4 M3 MIT Yes Details →
4.0.14 13 Apr 2019 C7 H5 M4 L1 MIT Yes Details →
4.1.2 13 Apr 2019 C7 H5 M3 L1 MIT Yes Details →
4.1.1 16 Mar 2019 C7 H6 M3 L1 MIT Yes Details →
4.0.13 07 Feb 2019 C7 H5 M4 L1 MIT Yes Details →
4.1.0 07 Feb 2019 C7 H6 M3 L1 MIT Yes Details →
3.0.6 02 Jan 2019 C3 H4 M3 MIT Yes Details →
3.0.5 15 Dec 2018 C3 H4 M3 MIT Yes Details →
3.0.4 15 Dec 2018 C3 H4 M3 MIT Yes Details →
4.0.12 04 Sep 2018 C7 H5 M4 L1 MIT Yes Details →
4.0.11 17 Oct 2017 C7 H5 M4 L1 MIT Yes Details →
4.0.10 21 May 2017 C7 H5 M4 L1 MIT Yes Details →
4.0.9 21 May 2017 C7 H5 M4 L1 MIT Yes Details →
4.0.8 02 May 2017 C7 H5 M4 L1 MIT Yes Details →
4.0.7 29 Apr 2017 C7 H5 M4 L1 MIT Yes Details →
4.0.6 13 Nov 2016 C7 H5 M4 L1 MIT Yes Details →
4.0.5 20 Nov 2015 C7 H5 M4 L1 MIT Yes Details →
4.0.4 29 Oct 2015 C7 H5 M4 L1 MIT Yes Details →
4.0.3 24 Sep 2015 C7 H5 M4 L1 MIT Yes Details →
4.0.2 04 Sep 2015 C7 H5 M4 L1 MIT Yes Details →
4.0.1 03 Sep 2015 C7 H5 M4 L1 MIT Yes Details →
4.0.0 01 Sep 2015 C7 H5 M4 L1 MIT Yes Details →
3.0.3 28 Apr 2015 C3 H4 M3 MIT Yes Details →
3.0.2 20 Apr 2015 C3 H4 M3 MIT Yes Details →
3.0.1 24 Mar 2015 C3 H4 M3 MIT Yes Details →
3.0.0 10 Feb 2015 C3 H4 M3 MIT Yes Details →
2.0.0 02 Sep 2014 C3 H4 M3 MIT Yes Details →
2.0.0-beta.1 26 Aug 2014 C3 H4 M3 MIT Yes Details →
2.0.0-alpha.4 20 May 2014 C3 H4 M3 MIT Yes Details →
2.0.0-alpha.3 20 May 2014 C3 H4 M3 MIT Yes Details →
2.0.0-alpha.2 06 Mar 2014 C3 H4 M3 MIT Yes Details →
2.0.0-alpha.1 10 Feb 2014 C3 H4 M3 MIT Yes Details →
1.3.0 02 Jan 2014 C3 H4 M3 MIT Yes Details →
1.2.1 26 Dec 2013 C3 H4 M3 MIT Yes Details →
1.2.0 24 Dec 2013 C3 H4 M3 MIT Yes Details →
1.1.2 06 Nov 2013 C3 H4 M3 non-standard Yes Details →
1.1.1 04 Nov 2013 C3 H4 M3 non-standard Yes Details →
1.1.0 04 Nov 2013 C3 H4 M3 non-standard Yes Details →
1.0.12 31 May 2013 C3 H4 M3 MIT Yes Details →
1.0.11 14 May 2013 C3 H4 M3 MIT Yes Details →
1.0.10 27 Feb 2013 C3 H4 M3 MIT Yes Details →
1.0.9 16 Feb 2013 C3 H4 M3 MIT Yes Details →
1.0.8 19 Jan 2013 C3 H4 M3 MIT Yes Details →
1.0.7 18 Sep 2012 C3 H4 M3 MIT Yes Details →
1.0.6-2 31 Jul 2012 C3 H4 M3 MIT Yes Details →
1.0.6 23 Jul 2012 C3 H4 M3 MIT Yes Details →
1.0.5-beta 09 Feb 2012 C3 H4 M3 MIT Yes Details →
1.0.4-beta 17 Jan 2012 C3 H4 M3 MIT Yes Details →
1.0.2-beta 22 Aug 2011 C3 H4 M3 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1
  • 2019 3
  • 2020 4
  • 2021 2
  • 2022 3
  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for handlebars

The 5 most severe of 25 vulnerabilities recorded for this package

Search all 25 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33937: Handlebars.js JavaScript Injection via AST Type Confusion 9.8 critical 4.7.9 27 Mar 2026
CVE-2026-106446: Handlebars JavaScript Injection Vulnerability via AST Type Confusion 9.8 critical 4.7.10 08 Oct 2026
CVE-2021-23383: Prototype Pollution in handlebars 9.8 critical 4.7.7 10 Feb 2022
CVE-2019-19919: Prototype Pollution in handlebars 9.8 critical 4.3.0 26 Dec 2019
CVE-2021-23369: Remote Code Execution in Handlebars 9.8 critical 4.7.7 06 May 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: 22/Oct/2026 · Vulnerabilities in our DB: 524167

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About handlebars

Is handlebars safe to use?

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

Vulert scores handlebars 64/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).

Is the latest version of handlebars affected?

No. 4.7.10, 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 handlebars should I use?

4.7.10 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 handlebars have?

25 vulnerabilities are recorded for handlebars in the npm ecosystem: 7 critical, 10 high, 7 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 handlebars vulnerabilities disclosed?

11 vulnerabilities were recorded for handlebars in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 handlebars 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 handlebars for upcoming vulnerabilities?

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