Handlebarsjs vulnerabilities
We track 5 vulnerabilities in Handlebarsjs products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on March 27, 2026.
Latest Handlebarsjs vulnerabilities
- 8.2 High severity
handlebars.js: Improper Neutralization of Input During Web Page Generation
Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, the Handlebars CLI precompiler (`bin/handlebars` / `lib/precompiler.js`) concatenates user-controlled strings — template file names and several CLI
- 8.1 High severity
handlebars.js: Improper Control of Generation of Code
Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, a crafted object placed in the template context can bypass all conditional guards in `resolvePartial()` and cause `invokePartial()` to return `undef
- 7.5 High severity
handlebars.js: Improper Check for Unusual or Exceptional Conditions
Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, when a Handlebars template contains decorator syntax referencing an unregistered decorator (e.g. `{{*n}}`), the compiled template calls `lookupPrope
- 8.1 High severity
handlebars.js: Improper Control of Generation of Code
Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, the `@partial-block` special variable is stored in the template data context and is reachable and mutable from within a template via helpers that ac
- 9.8 Critical severity
handlebars.js: Improper Control of Generation of Code
Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, `Handlebars.compile()` accepts a pre-parsed AST object in addition to a template string. The `value` field of a `NumberLiteral` AST node is emitted