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 undefined. The Handlebars runtime then treats the unresolved partial as a source that needs to be compiled, passing the crafted object to env.compile(). Because the object is a valid Handlebars AST containing injected code, the generated JavaScript executes arbitrary commands on the server. The attack requires the adversary to control a value that can be returned by a dynamic partial lookup. Version 4.7.9 fixes the issue. Some workarounds are available. First, use the runtime-only build (require('handlebars/runtime')). Without compile(), the fallback compilation path in invokePartial is unreachable. Second, sanitize context data before rendering: Ensure no value in the context is a non-primitive object that could be passed to a dynamic partial. Third, avoid dynamic partial lookups ({{> (lookup ...)}}) when context data is user-controlled.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-843",
"CWE-94"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33940.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:handlebarsjs:handlebars:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.7.9"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "68d8df5a88e0a26fe9e6084c5c6aaebe67b07da2"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v4.7.9",
"range": [
{
"fixed": "dce542c9a660048d31f0981ac8a45c08b919bddb"
}
],
"source": "REFERENCES_TAG"
}
]
}