Attack Chain

1. An attacker identifies an application using a vulnerable version of Thymeleaf (<= 3.1.3.RELEASE) that processes user-supplied input within a Thymeleaf template.
2. The attacker crafts a malicious payload containing Thymeleaf expression language syntax, specifically targeting the bypassable syntax patterns.
3. The attacker injects the crafted payload into a user-input field, such as a form parameter, URL parameter, or HTTP header, that is directly processed by the Thymeleaf template engine without proper validation or sanitization.
4. The vulnerable Thymeleaf engine processes the malicious payload, failing to properly neutralize the dangerous syntax patterns.
5. The injected expression is evaluated by the server, granting the attacker the ability to execute arbitrary code within the context of the application.
6. The attacker leverages the remote code execution capability to gain control of the server, potentially installing malware, accessing sensitive data, or pivoting to other systems within the network.
7. The attacker may establish persistent access by creating new user accounts, modifying system configurations, or deploying backdoors.

Impact

Successful exploitation of this SSTI vulnerability allows an unauthenticated remote attacker to execute arbitrary code on the server hosting the vulnerable application. This can lead to complete system compromise, including data theft, malware deployment, and denial of service. The severity is considered critical because it allows for remote code execution without authentication. Applications in any sector are vulnerable if they use Thymeleaf and pass user-provided input unsanitized to the template engine.

Recommendation

• Upgrade Thymeleaf to version 3.1.4.RELEASE or later to patch the vulnerability (CVE-2026-40478).
• Implement robust input validation and sanitization on all user-supplied data before passing it to the Thymeleaf template engine to prevent expression injection.
• Deploy the Sigma rule Detect Suspicious Thymeleaf Expression Injection to identify attempts to exploit this vulnerability in web server logs.
• Continuously monitor web application logs for unusual patterns and potential exploitation attempts related to Thymeleaf expressions.