Skip to main content
VulnerabilityPublished Updated

CVE-2026-106445: handlebars.js · Incomplete List of Disallowed Inputs

Affects handlebars.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.2 Critical : upgrade to 4.7.10 as a priority.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.7.10
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade handlebars.js and handlebars to 4.7.10.

Affected software

ProductAffectedFixed in
handlebars-langhandlebars.jsAffected
  • >=3.0.0 <4.7.10
Fixed in
  • 4.7.10
npmhandlebarspkg:npm/handlebarsOther threatsAffected
  • >=4.0.0 <4.7.10
Fixed in
  • 4.7.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade handlebars.js to version 4.7.10 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

Handlebars provides the power necessary to let users build semantic templates. From 3.0.0 until 4.7.10, Handlebars lookupProperty returns Function.prototype.constructor before applying the prototype-access deny list because constructor is an own property of Function.prototype. When an attacker can render a controlled template with allowProtoMethodsByDefault enabled and an accessible function in the template context, the template can traverse from that function through its prototype to Function.prototype and then obtain the Function constructor through the own-property bypass. This permits attacker-controlled JavaScript to execute with the server application's privileges. This issue is fixed in version 4.7.10.

References

Community reviews

Loading reviews…