Handlebars: JavaScript Injection via Unsafe Inline Embedding of Precompiled Templates
Published 8 Oct 2026 · Updated 8 Oct 2026
Affected package
- Affected
- >=4.0.0 <4.7.10
- Fixed in
- 4.7.10
npm install handlebars@4.7.10Details
Summary
Handlebars.precompile() generates JavaScript source that is commonly embedded in browser <script> elements. Before the fix, static template text containing </script> was emitted unchanged. HTML parsers recognize </script> even inside a JavaScript string literal, closing the surrounding script element and allowing following attacker-controlled markup to be parsed and executed.
This affects applications that precompile attacker-controlled templates and embed the generated source directly in an HTML <script> element. It does not affect ordinary server-side rendering or precompiled templates delivered as external JavaScript files.
Details
Static text is serialized by quotedString() in lib/handlebars/compiler/code-gen.js. The generated JavaScript is valid, but JavaScript quoting alone does not make it safe to embed in HTML. In HTML script data, the sequence </script> terminates the element regardless of JavaScript string context.
On affected releases, this template:
safe</script><script>alert("XSS")</script><script>could produce generated source containing:
return 'safe</script><script>alert("XSS")</script><script>';When included inline in an HTML document, the first </script> closes the script containing the precompiled template. The next <script> element is then parsed as HTML and executes.
Proof of Concept
const Handlebars = require('handlebars');
const template = 'safe</script><script>alert("XSS")</script><script>';
const output = Handlebars.precompile(template);
console.log(output.includes('</script>'));Affected versions print true. Embedding output directly in an inline <script> element allows the injected script tag to be parsed by the browser.
Workarounds
- Do not inline precompiled output from untrusted templates into HTML documents.
- Serve generated precompiled templates as external JavaScript files where practical.
Credits
Reported by Curly-Haired-Baboon Aka Laplas
Is GHSA-xw65-4hp5-5hc7 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected handlebars, and gives you the command that fixes it.
References
- Linkgithub.com/handlebars-lang/handlebars.js/security/advisories/GHSA-xw65-4hp5-5hc7
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-106444
- Linkgithub.com/handlebars-lang/handlebars.js/pull/2185
- Linkgithub.com/handlebars-lang/handlebars.js/commit/609d1b11c833c9a3e00f56f2f34d22f425446725
- Packagegithub.com/handlebars-lang/handlebars.js
- Linkgithub.com/handlebars-lang/handlebars.js/releases/tag/v4.7.10
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.