How to Fix CVE-2026-40478: Cwe-917: improper neutralization of special elements flaw in org.thymeleaf:thymeleaf-spring5
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 9.1 (Critical) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | thymeleaf < 3.1.4.RELEASE |
| Fixed in | thymeleaf 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring5 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring6 3.1.4.RELEASE |
| Type (CWE) | CWE-917: CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') |
What is CVE-2026-40478?
Thymeleaf is a server-side Java template engine for web and standalone environments. Versions 3.1.3.RELEASE and prior contain a security bypass vulnerability in the the expression execution mechanisms. Although the library provides mechanisms to prevent expression injection, it fails to properly neutralize specific syntax patterns that allow for the execution of unauthorized expressions. 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).
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s default-jdk 2>/dev/null | grep -i version
rpm -q default-jdk 2>/dev/null
default-jdk --version 2>/dev/null
Compare what you see against the Affected row above (thymeleaf < 3.1.4.RELEASE). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-40478
The primary fix is to upgrade org.thymeleaf:thymeleaf-spring5 to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: thymeleaf 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring5 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring6 3.1.4.RELEASE.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade default-jdk
default-jdk --version 2>/dev/null || dpkg -s default-jdk | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security default-jdk -y
rpm -q default-jdk
SUSE / openSUSE
sudo zypper patch --category security
rpm -q default-jdk
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-40478 affecting Java
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-40478-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detecting installed version of Java"
$pkg = winget list --id "Java" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\Java-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\Java" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to thymeleaf 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring5 3.1.4.RELEASE; org.t..."
winget upgrade --id "Java" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "Java"
Write-Host "Fix applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-40478 affecting Java
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-40478-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s default-jdk 2>/dev/null | grep -i version || echo "default-jdk not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q default-jdk || echo "default-jdk not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-40478-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/default-jdk /etc/default-jdk.d /etc/default-jdk.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: thymeleaf 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring5 3.1.4.RELEASE; org.t...)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y default-jdk
elif command -v dnf >/dev/null; then
dnf upgrade --security -y default-jdk
elif command -v yum >/dev/null; then
yum update -y default-jdk
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s default-jdk 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q default-jdk
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop default-jdk
sudo systemctl disable default-jdk
How to verify the fix worked
# Linux
default-jdk --version 2>/dev/null || dpkg -s default-jdk | grep -i version
rpm -q default-jdk 2>/dev/null || true
# Windows
winget list | findstr /I "default-jdk"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above thymeleaf 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring5 3.1.4.RELEASE; org.thymeleaf:thymeleaf-spring6 3.1.4.RELEASE. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-40971: Spring Boot (Bundle Sibling) — Spring Boot (Bundle Sibling)
- How to Fix CVE-2026-22744: Critical Vulnerability in Spring AI — Critical Vulnerability in Spring AI
- How to Fix CVE-2026-22735: Server Sent Event stream corruption in Spring Foundation , Server Sent Event stream corruption in Spring Foundation
- How to Fix CVE-2026-40969: CWE-209: Generation of Error Message Containing Sensitive Information , CWE-209: Generation of Error Message Containing Sensitive Information
- How to Fix CVE-2026-40970: CWE-295: Improper Certificate Validation in Spring Boot , CWE-295: Improper Certificate Validation in Spring Boot
Is CVE-2026-40478 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
9.1 (critical). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://github.com/thymeleaf/thymeleaf/security/advisories/GHSA-xjw8-8c5c-9r79
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40478
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*