Is handlebars 4.1 vulnerable?
npm · 3 releases from 4.1.0 to 4.1.2 · latest handlebars is 4.7.10 · checked 1 Nov 2026
Yes: 19 known advisories
Yes. handlebars 4.1.2, the last 4.1 release, is affected by 19 known security advisories (6 critical, 9 high, 3 medium, 1 low), including CVE-2026-106446, CVE-2026-106445, CVE-2026-33937. 1 more affects earlier 4.1.x releases. Upgrade to 4.7.10 or later to fix all of them.
npm install handlebars@4.7.10Advisories affecting handlebars 4.1.2
Handlebars: JavaScript Injection via Unsafe Inline Embedding of Precompiled Templates
- Affected
- >=4.0.0 <4.7.10
- Fixed in
- 4.7.10
Handlebars: JavaScript Injection via AST Type Confusion in compile (bypass of CVE-2026-33937)
- Affected
- >=4.0.0 <4.7.10
- Fixed in
- 4.7.10
Handlebars: JavaScript Injection via Own Property Check Bypass
- Affected
- >=3.0.0 <4.7.10
- Fixed in
- 4.7.10
Handlebars.js has a Property Access Validation Bypass in container.lookup
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has JavaScript Injection in CLI Precompiler via Unescaped Names and Options
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has JavaScript Injection via AST Type Confusion when passing an object as dynamic partial
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has Denial of Service via Malformed Decorator Syntax in Template Compilation
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has JavaScript Injection via AST Type Confusion by tampering @partial-block
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has JavaScript Injection via AST Type Confusion
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Handlebars.js has Prototype Pollution Leading to XSS through Partial Template Injection
- Affected
- >=4.0.0 <4.7.9
- Fixed in
- 4.7.9
Prototype Pollution in handlebars
- Affected
- <4.7.7
- Fixed in
- 4.7.7
Regular Expression Denial of Service in Handlebars
- Affected
- >=4.0.0 <4.4.5
- Fixed in
- 4.4.5
Arbitrary Code Execution in Handlebars
- Affected
- <3.0.8 · >=4.0.0 <4.5.3
- Fixed in
- 3.0.8, 4.5.3
Remote code execution in handlebars when compiling templates
- Affected
- <4.7.7
- Fixed in
- 4.7.7
Arbitrary Code Execution in handlebars
- Affected
- <3.0.8 · >=4.0.0 <4.5.3
- Fixed in
- 3.0.8, 4.5.3
Prototype Pollution in handlebars
- Affected
- <3.0.8 · >=4.0.0 <4.5.3
- Fixed in
- 3.0.8, 4.5.3
Arbitrary Code Execution in handlebars
- Affected
- <3.0.8 · >=4.0.0 <4.5.2
- Fixed in
- 3.0.8, 4.5.2
Denial of Service in handlebars
- Affected
- >=4.0.0 <4.4.5
- Fixed in
- 4.4.5
Prototype Pollution in handlebars
- Affected
- >=4.0.0 <4.3.0 · <3.0.8
- Fixed in
- 3.0.8, 4.3.0
Fixed within 4.1.x, affecting earlier releases
Prototype Pollution in handlebars
- Affected
- >=4.1.0 <4.1.2 · >=4.0.0 <4.0.14 · <3.0.7
- Fixed in
- 3.0.7, 4.0.14, 4.1.2
Which of your client projects are still on handlebars 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact handlebars version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other handlebars versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.