Thymeleaf End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Thymeleaf versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Thymeleaf 3.1 is supported, with no end-of-life or end-of-support date announced yet. 1 tracked Thymeleaf version is declared end of life without a published date. The full Thymeleaf lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/thymeleaf)
Thymeleaf lifecycle status — the real story
Thymeleaf, the server-side Java template engine (thymeleaf.org, Maven coordinates org.thymeleaf:thymeleaf, with the Spring integration modules thymeleaf-spring5 and thymeleaf-spring6 released on the same version numbers); one line per minor version, 3.0 and 3.1. Release days are the Maven Central publish dates from repo1.maven.org/maven2/org/thymeleaf/thymeleaf, the directory listing and maven-metadata.xml agreeing on both ends of every line and matching the publish times on central.sonatype.com. Maven versions carry a .RELEASE suffix; the plain number is shown. 3.1 is the current line and carries the latest release.
End-of-life rule: the project's security policy (SECURITY.md in the Thymeleaf repository, shown as its GitHub security policy) says that, in general, only the latest minor version is considered supported and receives timely updates and security patches; when 3.1 became the production line the same file stated that 3.0.x and earlier are no longer supported and that no further maintenance or security patches are planned for them. 3.1 is therefore served as supported and 3.0 as end of life. The project names no calendar end date for either line, so none is shown. The critical expression-sandbox bypasses CVE-2026-40477, CVE-2026-40478 and CVE-2026-41901 were fixed upstream only in 3.1.4 and 3.1.5 (GitHub advisories GHSA-r4v4-5mwr-2fwr, GHSA-xjw8-8c5c-9r79 and GHSA-c9ph-gxww-7744); the last 3.0 release carries them unfixed.
Commercial context: HeroDevs Never-Ending Support covers Thymeleaf 3.0.x (docs.herodevs.com/thymeleaf: upstream Maven coordinates org.thymeleaf:thymeleaf with an NES version on the HeroDevs registry; the release notes list 3.0.16 as the initial supported baseline, identical to upstream 3.0.15, and 3.0.17 as the release fixing the three CVEs above). HeroDevs states that release fixes the core module only, not the Spring integration modules. That is a paid offering for the 3.0 line; it is not a project release and its builds are not published to Maven Central.
Thymeleaf release and support pattern
Of the 2 release lines tracked, 1 is past end of life and 1 is still within support; 1 is marked end of life without a published date. The newest line, 3.1, was released November 16, 2022. No end-of-life date is currently published for the 1 supported line.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Thymeleaf end of life mean for your organization?
When a version of Thymeleaf reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Thymeleaf should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Thymeleaf reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Thymeleaf versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Thymeleaf has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Thymeleaf exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Thymeleaf 3.0. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."