Visit NES for Thymeleaf Home Page
NES for Thymeleaf 3.0.x Release Notes
2 versions
Comprehensive release notes and changelog for NES for Thymeleaf 3.0.x, including security patches, bug fixes, and feature updates across all supported versions.
October 2026
3.0.17
Released Oct 7, 2026 Full Version:
3.0.15-thymeleaf-3.0.17
Security Fixes
- CVE-2026-40477 (Critical) - Restricted expression mode bypass through expression objects. Thymeleaf evaluates expressions that may carry untrusted input in a restricted mode, which forbids instantiation and static access and wraps the request. That mode still handed the
#ctx,#vars,#root,#thisand#execInfoexpression objects to an injected expression, so it could reach the live context, including the unwrapped request. Restricted expressions now reject those five objects. See Breaking Changes before upgrading. - CVE-2026-40478 (Critical) - Restricted expression mode bypass through unneutralized syntax patterns. The restricted-mode check for
new, static access andparamscanned the expression as written, so whitespace and control characters reached it unchanged. Separately, type references in expressions were checked only against a short list ofjava.*classes. Expressions are now normalized before the check, and type references to classes in sensitive packages, such as Javassist, Byte Buddy, Jackson and Spring, are rejected. See Breaking Changes before upgrading. - CVE-2026-41901 (Critical) - Restricted expression mode bypass through mixed-case keywords. The restricted-mode check matched
newandparamcase-sensitively, so forms such asNEWorpArAmpassed it. The check now matches them in any letter case. See Breaking Changes and Notes before upgrading.
Breaking Changes
- Restricted expressions can no longer read
#ctx,#vars,#root,#thisor#execInfo. The CVE-2026-40477 fix rejects these objects in every restricted context, including harmless reads. Restricted contexts includeth:utext, text-mode output and inlining, preprocessing, and fragment and link expressions. A text-mode[# th:text="${#execInfo.templateName}"]that worked before now fails withAccess to variable '#execInfo' is forbidden in this context.Expressions in non-restricted contexts, such as an escapedth:textin an HTML template, can still use them. newandparamare rejected in any letter case in restricted expressions. After the CVE-2026-41901 fix, a standalone word such asNeworPARAMfails the check, including inside a string literal. For example,th:utext="${'New York'}"now fails withInstantiation of new objects and access to static classes or parameters is forbidden in this context. The lower-case forms were already rejected.- Type references to classes in blocked packages fail in every expression. The CVE-2026-40478 and CVE-2026-41901 fixes reject
newand static access (@...@) on classes in packages such as Spring, Jackson, Netty, Groovy, Kotlin, Scala and Jetty, in normal expressions as well as restricted ones. The expression fails withAccess is forbidden for type '<class>' in Thymeleaf expressions. Calling methods on existing objects of those classes still works.
Notes
- This release fixes the core
org.thymeleaf:thymeleafmodule, which is the artifact NES for Thymeleaf ships. Each of these advisories also lists the Spring integration modules, where upstream's fix includes changes to how SpEL expressions are evaluated. Those modules aren't part of this release, so an application that renders templates throughthymeleaf-spring5orthymeleaf-spring4remains exposed through SpEL. In such an application, don't pass unvalidated user input to the template engine or into restricted expression contexts. - In the core module, which evaluates expressions with OGNL, the mixed-case and control-character variants of CVE-2026-40478 and CVE-2026-41901 make OGNL fail to parse the expression rather than bypass the check. The fixes reject them before parsing, as upstream does.
3.0.16
Released Oct 6, 2026 Full Version:
3.0.15-thymeleaf-3.0.16
Notes
- This release originates from the open-source Thymeleaf project forked by HeroDevs. It encompasses modifications implemented by HeroDevs to ensure successful framework builds.
- This is the initial supported baseline for the 3.0.x line. It is functionally identical to upstream 3.0.15.RELEASE, with no behavioral changes, and contains no vulnerability patches. Security fixes are delivered in subsequent releases on this line.
Stay in the loop
~/herodevs-spring-framework-support
herodevs@nes:open-source$ ./display-support-info.sh