CriticalGHSA-r4v4-5mwr-2fwrCVE-2026-40477

Improper restriction of the scope of accessible objects in Thymeleaf expressions

Published 15 Apr 2026 · Updated 5 May 2026

Is your project on an affected org.thymeleaf:thymeleaf?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<3.1.4.RELEASE
Fixed in
3.1.4.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.thymeleaf:thymeleaf -DdepVersion=3.1.4.RELEASE -DforceVersion=true
Affected
<3.1.4.RELEASE
Fixed in
3.1.4.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.thymeleaf:thymeleaf-spring5 -DdepVersion=3.1.4.RELEASE -DforceVersion=true
Affected
<3.1.4.RELEASE
Fixed in
3.1.4.RELEASE
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.thymeleaf:thymeleaf-spring6 -DdepVersion=3.1.4.RELEASE -DforceVersion=true

Details

Impact

A security bypass vulnerability exists in the expression execution mechanisms of Thymeleaf up to and including 3.1.3.RELEASE. Although the library provides mechanisms to prevent expression injection, it fails to properly restrict the scope of accessible objects, allowing specific potentially sensitive objects to be reached from within a template. If an application developer passes unvalidated user input directly to the template engine, an unauthenticated remote attacker can bypass the library's protections to achieve Server-Side Template Injection (SSTI).

Patches

This has been fixed in Thymeleaf 3.1.4.RELEASE.

Workarounds

No workaround is available beyond ensuring applications do not pass unvalidated user input directly to the template engine. Upgrading to 3.1.4.RELEASE is strongly recommended in any case.

Credits

Thanks to Thomas Reburn (Praetorian) for responsible disclosure.

Is GHSA-r4v4-5mwr-2fwr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.thymeleaf:thymeleaf, and gives you the command that fixes it.

More advisories for org.thymeleaf:thymeleaf

  • CriticalCVE-2026-41901Sandboxed Thymeleaf expressions vulnerable to improper recognition of unauthorized syntax patterns · 4 May 2026
  • CriticalCVE-2026-40478Improper neutralization of specific syntax patterns for unauthorized expressions in Thymeleaf · 15 Apr 2026
org.thymeleaf:thymeleaf security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.