Apache Tomcat End of Life: Tomcat 9 is EOL — Migration Guide to Tomcat 10/11

May 30, 2026 · 5:21 AM UTC ·3 min read · 0 reactions · 0 comments · 43 views

#java #security #devops #opensource #migration

Apache Tomcat End of Life: Tomcat 9 is EOL — Migration Guide to Tomcat 10/11

TL;DR · WeSearch summary

Apache Tomcat 9 has reached its end of life as of December 31, 2025, meaning it will no longer receive security patches or CVE fixes. Many production servers continue to run Tomcat 9 due to the complexities involved in migrating to newer versions. The migration from Tomcat 9 to Tomcat 10 or 11 requires significant changes to application code, making it a challenging process for many teams.

Key facts

▪Tomcat 9 is the last version to use the javax.* namespace, while Tomcat 10 and later use the jakarta.* namespace.
▪The Apache Tomcat project has stopped backporting fixes for vulnerabilities after Tomcat 9's EOL date.
▪Migrating directly to Tomcat 11 is recommended as it has no defined EOL date, unlike Tomcat 10.1 which reaches EOL in December 2026.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/endoflifeai/apache-tomcat-end-of-life-tomcat-9-is-eol-migration-guide-to-tomcat-1011-5hk6
Publication time	Sat, 30 May 2026 05:21:04 +0000
Retrieval time	2026-05-30T05:42:06.163Z
Last seen	2026-05-30T05:42:06.163Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	kjTEMbfohUOQ
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3921242) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } endoflife-ai Posted on May 30 • Originally published at endoflife.ai Apache Tomcat End of Life: Tomcat 9 is EOL — Migration Guide to Tomcat 10/11 #java #security #devops #opensource Apache Tomcat 9 reached end of life on December 31, 2025. No more security patches. No more CVE fixes. Every vulnerability disclosed from January 1, 2026 onward is permanently unpatched on Tomcat 9. And yet — tens of thousands of production servers are still running it today. This isn't negligence.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments