CVE-2026-55760: jknack handlebars.java · Path Traversal
Affects jknack handlebars.javaSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 4.5.2 soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade handlebars.java and com.github.jknack/handlebars.java to 4.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jknackhandlebars.java | Affected
| Fixed in
|
Mavencom.github.jknack/handlebars.javapkg:maven/com.github.jknack/handlebars.javaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade handlebars.java to version 4.5.2 or later, where this path traversal vulnerability is fixed. No other mitigation is specified or required.
Description
Handlebars.java provides logic-less and semantic Mustache templates with Java. Prior to 4.5.2, applications that pass user-controlled input to Handlebars.compile() using FileTemplateLoader or ClassPathTemplateLoader are vulnerable to path traversal, allowing arbitrary file read through template names derived from URL path parameters, request parameters, or other user-controlled sources. This issue is fixed in version 4.5.2.