Tomcat (Spring Boot) · Release roundup · 11 CVEs
Tomcat Nov release
Next cycleRoundupCISA says 9.1, Apache says Low. Off-by-default features.
Apache disclosed 11 Tomcat vulnerabilities on 19 Nov 2026: 1 critical, 4 important, 2 moderate and 4 low. All but one need a feature you have to turn on, such as HTTP/2, the RewriteValve or clustering, and none has a public exploit or reported attacks. The "9.1 critical" posts come from scores CISA added to the CVE records; Apache rates that bug Low. Fixed releases are out for all but two cluster bugs.
How scary is it?
The bugs 11 advisories
CriticalTomcat Cluster TLS-PSK on TLS 1.3 lets any node joinPatch now if…
Only clusters secured with TLS-PSK on TLS 1.3, and only on 11.0.29, 10.1.62 and 9.0.124 (Apache also lists 11.0.28, which was never released). No fixed release yet: use TLS 1.2 until 11.0.30, 10.1.63 or 9.0.125.
HighTomcat HTTP/2 connection setup can cause a DoSNext cycle
Only with HTTP/2 turned on: it's commented out in the shipped server.xml and off by default in Spring Boot. Apache: a resource isn't released during HTTP/2 connection setup, which "could lead to a DoS".
HighTomcat Rewrite rules don't stop the requestNext cycle
Only with the RewriteValve (off by default) and a rule using the [F], [G] or [R] flag. Tomcat keeps processing a request such a rule should have stopped; Apache calls it execution after redirect.
HighTomcat ExpiresFilter strips Cache-Control: privateNext cycle
Only with the ExpiresFilter (not in the default web.xml) on pages behind Tomcat's login. It removes the header Tomcat sets so proxies don't cache protected pages; it matters if a shared cache or CDN sits in front.
HighTomcat WebSocket memory leak with the OWB moduleNext cycle
Only with Tomcat's optional OpenWebBeans (OWB) module and WebSocket. The module isn't shipped as a download; you have to build it from source.
2 medium and 4 low: opt-in features or low impact
- MediumTomcatCVE-2026-95517
- MediumTomcatCVE-2026-118436
- LowTomcatCVE-2026-116561
- LowTomcatCVE-2026-118233
- LowTomcatCVE-2026-106012
- LowTomcatCVE-2026-117517
Are you affected? only if all are true
1Tomcat before 11.0.29 / 10.1.62 / 9.0.124command
Every earlier 11.0, 10.1 and 9.0 release; end-of-life 8.5 and older get no fixes. The critical cluster bug is the exception: it affects only 11.0.29, 10.1.62 and 9.0.124. Spring Boot embeds Tomcat, and its newest releases (4.2.0, 4.1.3 and 4.0.10) still bring in 11.0.27; check with ./mvnw dependency:tree -Dincludes=org.apache.tomcat.embed.1,2,3,13,14
$CATALINA_HOME/bin/version.sh2You turned on an affected featurecommand
Ten of the 11 need something you add: HTTP/2 (an Http2Protocol line inside a <Connector>; in Spring Boot, server.http2.enabled), the RewriteValve, the ExpiresFilter, CGI, Jakarta Authentication, clustering, an AJP load balancer or the OWB module. The shipped files contain commented-out examples, so matches inside <!-- --> don't count. Check your apps' WEB-INF/web.xml and META-INF/context.xml too. The eleventh, a low-rated memory leak (CVE-2026-118233), needs an app that uses the HTTP upgrade API; Apache only says "some circumstances".1,10,11,16,17
grep -rnE 'Http2Protocol|RewriteValve|ExpiresFilter|CGIServlet|<Cluster|LoadBalancerDrainingValve|OpenWebBeans' $CATALINA_BASE/conf/What to do
1Upgrade to 11.0.29, 10.1.62 or 9.0.124
Released 13 to 16 Nov 2026, these fix 10 of the 11 bugs. Tomcat 8.5 gets no fixes (end of life since 31 Mar 2024), and 9.0 support ends on 31 Mar 2027.12,13,1,2,3
Latest safe versions checked 21 Nov
2Spring Boot: set the Tomcat version
No Spring Boot release brings in a fixed Tomcat yet. Set the tomcat.version property to 11.0.29 in your build, the documented way to override a version Spring Boot manages. HTTP/2 is off unless you set server.http2.enabled.14,15,16
3Clusters: stay on TLS 1.2Pending · expected 28 Nov
If your cluster uses TLS-PSK, keep it on TLS 1.2: on TLS 1.3 a node without the key can join (CVE-2026-133325). The fix comes in 11.0.30, 10.1.63 and 9.0.125; Apache hasn't announced a date, and we'll check again by 28 Nov 2026. The old EncryptInterceptor won't be fixed (CVE-2026-95517): move to TLS-PSK on TLS 1.2.7,8,1
4Don't panic over the 9.1
The scary numbers come from CISA's automated scoring added to the CVE records, not from Apache: 9.1 on CVE-2026-116561, which Apache rates Low, meaning "extremely hard to exploit" or with "minimal consequences". Apache's own ratings: one critical (the cluster bug), four important.5,4,6,1
This page shows you how to check. It can't tell you you're safe.
Sources (17) and changelog
- Apache Tomcat 11 security page: all 11 bugs, ratings, affected versions 19 Nov
- Apache Tomcat 10 security page: fixed in 10.1.62 19 Nov
- Apache Tomcat 9 security page: fixed in 9.0.124 19 Nov
- Apache Tomcat: what Low, Moderate, Important and Critical mean
- CVE record CVE-2026-116561: Apache "low", CISA score 9.1, exploitation none
- CVE record CVE-2026-133325: Apache "critical", CISA score 9.8
- Tomcat announce: CVE-2026-133325 cluster TLS-PSK, use TLS 1.2 19 Nov
- Tomcat announce: CVE-2026-95517 EncryptInterceptor not fixed, move to TLS-PSK 19 Nov
- CISA KEV catalog: none of the 11 listed
- Tomcat source: shipped server.xml, HTTP/2, AJP and cluster commented out
- Tomcat docs: CGI is disabled by default
- Apache Tomcat: latest releases, 9.0 end of support 31 Mar 2027
- Apache Tomcat: 8.5 end of life 31 Mar 2024
- Maven Central: Spring Boot 4.1.3 manages Tomcat 11.0.27 (4.2.0 and 4.0.10 too)
- Spring Boot docs: override a managed version with a property
- Spring Boot docs: server.http2.enabled defaults to false
- Tomcat docs: the OWB module must be built from source
- Published.