CVE-2026-63490

HighCVSS 7.5

Published: 20/08/2026(UTC)Updated: 25/08/2026(UTC)Translated: 20/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.47%

39th percentile - higher than 39% of all known CVEs

Summary

Handlebars.java before version 4.5.3 contains a file read vulnerability. SpringTemplateLoader does not properly validate view names, allowing a remote attacker to read files accessible to the JVM when an application exposes a controller with a user-influenced view name. Fixed in version 4.5.3.

Risk Assessment

An attacker can read sensitive files from the server, such as configurations, credentials, or user data, leading to information disclosure.

Recommendation

Update Handlebars.java to version 4.5.3 or later, which includes the fix.

Other vulnerabilities in Handlebars.java

CVE-2026-55760High
A path traversal vulnerability in Handlebars.java allows arbitrary file read. Applications passing user-controlled input to Handlebars.compile() with FileTemplateLoader or ClassPathTemplateLoader are affected.

Original NVD description (English source)

Handlebars.java provides logic-less and semantic Mustache templates with Java. Prior to 4.5.3, com.github.jknack.handlebars.springmvc.SpringTemplateLoader resolves attacker-influenced Spring MVC view names through Spring ResourceLoader without the path-containment validation used by other URL-based loaders. In handlebars-springmvc/src/main/java/com/github/jknack/handlebars/springmvc/SpringTemplateLoader.java, a view name using a file: or classpath: URL and ending with the # fragment delimiter places the appended .hbs suffix in the fragment, which FileUrlResource.exists() and URL.openStream() discard. HandlebarsViewResolver in handlebars-springmvc/src/main/java/com/github/jknack/handlebars/springmvc/HandlebarsViewResolver.java then passes the attacker-controlled name to handlebars.compile(), allowing an unauthenticated remote attacker to read files accessible to the JVM when an application exposes a controller with a user-influenced view name. This issue is fixed in version 4.5.3.