Author: markt
Date: Tue Oct 20 13:27:49 2026
New Revision: 1939289
Log:
Publish CVEs fixed in October release round
Modified:
tomcat/site/trunk/docs/security-10.html
tomcat/site/trunk/docs/security-11.html
tomcat/site/trunk/docs/security-9.html
tomcat/site/trunk/xdocs/security-10.xml
tomcat/site/trunk/xdocs/security-11.xml
tomcat/site/trunk/xdocs/security-9.xml
Modified: tomcat/site/trunk/docs/security-10.html
==============================================================================
--- tomcat/site/trunk/docs/security-10.html Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/docs/security-10.html Tue Oct 20 13:27:49 2026
(r1939289)
@@ -42,7 +42,102 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><li><a href="#Fixed_in_Apache_Tomcat_10.1.60">Fixed in Apache Tomcat
10.1.60</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.59">Fixed in Apache
Tomcat 10.1.59</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.57">Fixed in
Apache Tomcat 10.1.57</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.56">Fixed in Apache Tomcat
10.1.56</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.55">Fixed in Apache
Tomcat 10.1.55</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.54">Fixed in
Apache Tomcat 10.1.54</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.53">Fixed in Apache Tomcat
10.1.53</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.52">Fixed in Apache
Tomcat 10.1.52</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.50">Fixed in
Apache Tomcat 10.1.50</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.47">Fixed in Apache Tomcat
10.1.47</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.45">Fixed in Apache
Tomcat 10.1.45</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.44">Fixed in
Apache Tomcat 10.1.44</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.43">Fixed in Apache Tomcat
10.1.43</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.42">Fixed in Apache
Tomcat 10.1.42</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.41">Fixed in
Apache Tomcat 10.1.41</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.40">Fixed in Apache Tomcat
10.1.40</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.39">Fixed in Apache
Tomcat 10.1.39</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.35">Fixed in
Apache Tomcat 10.1.35</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.34">Fixed in Apache Tomcat
10.1.34</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.33">Fixed in Apache
Tomcat 10.1.33</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.31">Fixed in
Apache Tomcat 10.1.31</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.25">Fixed in Apache Tomcat
10.1.25</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.19">Fixed in Apache
Tomcat 10.1.19</a></li><li><a href="#Fixed_in_Apache_T
omcat_10.1.16">Fixed in Apache Tomcat 10.1.16</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.14">Fixed in Apache Tomcat
10.1.14</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.13">Fixed in Apache
Tomcat 10.1.13</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.9">Fixed in
Apache Tomcat 10.1.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.8">Fixed
in Apache Tomcat 10.1.8</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.6">Fixed in Apache Tomcat
10.1.6</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.5">Fixed in Apache
Tomcat 10.1.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.2">Fixed in
Apache Tomcat 10.1.2</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.1">Fixed
in Apache Tomcat 10.1.1</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.27">Fixed in Apache Tomcat
10.0.27</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.23">Fixed in Apache
Tomcat 10.0.23</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.0-M17">Fixed
in Apache Tomcat 10.1.0-M17</a></li><li><a href="#
Fixed_in_Apache_Tomcat_10.0.21">Fixed in Apache Tomcat 10.0.21</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.0-M15">Fixed in Apache Tomcat
10.1.0-M15</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.20">Fixed in
Apache Tomcat 10.0.20</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.0-M14">Fixed in Apache Tomcat
10.1.0-M14</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.16">Fixed in
Apache Tomcat 10.0.16</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.0-M10">Fixed in Apache Tomcat
10.1.0-M10</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.12">Fixed in
Apache Tomcat 10.0.12</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.0-M6">Fixed in Apache Tomcat
10.1.0-M6</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.7">Fixed in Apache
Tomcat 10.0.7</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.6">Fixed in
Apache Tomcat 10.0.6</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.5">Fixed
in Apache Tomcat 10.0.5</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.4">Fixed in Apache
Tomcat 10.0.4</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.2">Fixed in
Apache Tomcat 10.0.2</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M10">Fixed in Apache Tomcat
10.0.0-M10</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.0-M8">Fixed in
Apache Tomcat 10.0.0-M8</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M7">Fixed in Apache Tomcat
10.0.0-M7</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.0-M6">Fixed in
Apache Tomcat 10.0.0-M6</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M5">Fixed in Apache Tomcat
10.0.0-M5</a></li><li><a href="#Not_a_vulnerability_in_Tomcat">Not a
vulnerability in Tomcat</a></li></ul>
+ <ul><li><a href="#Fixed_in_Apache_Tomcat_10.1.61">Fixed in Apache Tomcat
10.1.61</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.60">Fixed in Apache
Tomcat 10.1.60</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.59">Fixed in
Apache Tomcat 10.1.59</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.57">Fixed in Apache Tomcat
10.1.57</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.56">Fixed in Apache
Tomcat 10.1.56</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.55">Fixed in
Apache Tomcat 10.1.55</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.54">Fixed in Apache Tomcat
10.1.54</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.53">Fixed in Apache
Tomcat 10.1.53</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.52">Fixed in
Apache Tomcat 10.1.52</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.50">Fixed in Apache Tomcat
10.1.50</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.47">Fixed in Apache
Tomcat 10.1.47</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.45">Fixed in
Apache Tomcat 10.1.45</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.44">Fixed in Apache Tomcat
10.1.44</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.43">Fixed in Apache
Tomcat 10.1.43</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.42">Fixed in
Apache Tomcat 10.1.42</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.41">Fixed in Apache Tomcat
10.1.41</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.40">Fixed in Apache
Tomcat 10.1.40</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.39">Fixed in
Apache Tomcat 10.1.39</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.35">Fixed in Apache Tomcat
10.1.35</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.34">Fixed in Apache
Tomcat 10.1.34</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.33">Fixed in
Apache Tomcat 10.1.33</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.31">Fixed in Apache Tomcat
10.1.31</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.25">Fixed in Apache
Tomcat 10.1.25</a></li><li><a href="#Fixed_in_Apache_T
omcat_10.1.19">Fixed in Apache Tomcat 10.1.19</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.16">Fixed in Apache Tomcat
10.1.16</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.14">Fixed in Apache
Tomcat 10.1.14</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.13">Fixed in
Apache Tomcat 10.1.13</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.9">Fixed in Apache Tomcat
10.1.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.8">Fixed in Apache
Tomcat 10.1.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.6">Fixed in
Apache Tomcat 10.1.6</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.5">Fixed
in Apache Tomcat 10.1.5</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.1.2">Fixed in Apache Tomcat
10.1.2</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.1">Fixed in Apache
Tomcat 10.1.1</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.27">Fixed in
Apache Tomcat 10.0.27</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.23">Fixed in Apache Tomcat
10.0.23</a></li><li><a href="#Fixed_
in_Apache_Tomcat_10.1.0-M17">Fixed in Apache Tomcat 10.1.0-M17</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.21">Fixed in Apache Tomcat
10.0.21</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.0-M15">Fixed in
Apache Tomcat 10.1.0-M15</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.20">Fixed in Apache Tomcat
10.0.20</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.0-M14">Fixed in
Apache Tomcat 10.1.0-M14</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.16">Fixed in Apache Tomcat
10.0.16</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.0-M10">Fixed in
Apache Tomcat 10.1.0-M10</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.12">Fixed in Apache Tomcat
10.0.12</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.1.0-M6">Fixed in Apache
Tomcat 10.1.0-M6</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.7">Fixed in
Apache Tomcat 10.0.7</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.6">Fixed
in Apache Tomcat 10.0.6</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.5">Fixed in Apac
he Tomcat 10.0.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.4">Fixed in
Apache Tomcat 10.0.4</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.2">Fixed
in Apache Tomcat 10.0.2</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M10">Fixed in Apache Tomcat
10.0.0-M10</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.0-M8">Fixed in
Apache Tomcat 10.0.0-M8</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M7">Fixed in Apache Tomcat
10.0.0-M7</a></li><li><a href="#Fixed_in_Apache_Tomcat_10.0.0-M6">Fixed in
Apache Tomcat 10.0.0-M6</a></li><li><a
href="#Fixed_in_Apache_Tomcat_10.0.0-M5">Fixed in Apache Tomcat
10.0.0-M5</a></li><li><a href="#Not_a_vulnerability_in_Tomcat">Not a
vulnerability in Tomcat</a></li></ul>
+ </div><h3 id="Fixed_in_Apache_Tomcat_10.1.61"><span
class="pull-right">2026-10-12</span> Fixed in Apache Tomcat 10.1.61</h3><div
class="text">
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101356"
rel="nofollow">CVE-2026-101356</a></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/6c7da60893bd186d6cb2df7330299d7e70e68279">6c7da608</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.55 to 10.1.60</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101296"
rel="nofollow">CVE-2026-101296</a></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/8fafc6f263311b7a0b7ce67477822175d1adf7ce">8fafc6f2</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.60</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-93446"
rel="nofollow">CVE-2026-93446</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/ccbe01a52a9b255ad98e71b5bed76ed10a099503">ccbe01a5</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.25 to 10.1.60</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88041"
rel="nofollow">CVE-2026-88041</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/395bcafcfcf2e1cff451a5785361679931b49a79">395bcafc</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.27 to 10.1.60</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74049"
rel="nofollow">CVE-2026-74049</a></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/f8023d833675f00968b89b45639210d3c7dcc95d">f8023d83</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.60</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74048"
rel="nofollow">CVE-2026-74048</a></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/5561032ca9d2bf32fafd8a8a417692c9826e30fe">5561032c</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.22 to 10.1.60</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_10.1.60"><span
class="pull-right">2026-09-15</span> Fixed in Apache Tomcat 10.1.60</h3><div
class="text">
<p><strong>Low: WebSocket message smuggling with
Modified: tomcat/site/trunk/docs/security-11.html
==============================================================================
--- tomcat/site/trunk/docs/security-11.html Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/docs/security-11.html Tue Oct 20 13:27:49 2026
(r1939289)
@@ -36,7 +36,119 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><li><a href="#Fixed_in_Apache_Tomcat_11.0.26">Fixed in Apache Tomcat
11.0.26</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.25">Fixed in Apache
Tomcat 11.0.25</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.24">Fixed in
Apache Tomcat 11.0.24</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.23">Fixed in Apache Tomcat
11.0.23</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.22">Fixed in Apache
Tomcat 11.0.22</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.21">Fixed in
Apache Tomcat 11.0.21</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.20">Fixed in Apache Tomcat
11.0.20</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.18">Fixed in Apache
Tomcat 11.0.18</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.15">Fixed in
Apache Tomcat 11.0.15</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.12">Fixed in Apache Tomcat
11.0.12</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.11">Fixed in Apache
Tomcat 11.0.11</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.10">Fixed in
Apache Tomcat 11.0.10</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.9">Fixed in Apache Tomcat
11.0.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.8">Fixed in Apache
Tomcat 11.0.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.7">Fixed in
Apache Tomcat 11.0.7</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.6">Fixed
in Apache Tomcat 11.0.6</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.5">Fixed in Apache Tomcat
11.0.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.3">Fixed in Apache
Tomcat 11.0.3</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.2">Fixed in
Apache Tomcat 11.0.2</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.1">Fixed
in Apache Tomcat 11.0.1</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0">Fixed in Apache Tomcat
11.0.0</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M21">Fixed in Apache
Tomcat 11.0.0-M21</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M17">Fixed in Apache Tomcat
11.0.0-M17</a></li><li><a href="#Fixed_in_Apache_Tomcat_
11.0.0-M12">Fixed in Apache Tomcat 11.0.0-M12</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M11">Fixed in Apache Tomcat
11.0.0-M11</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M6">Fixed in
Apache Tomcat 11.0.0-M6</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M5">Fixed in Apache Tomcat
11.0.0-M5</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M3">Fixed in
Apache Tomcat 11.0.0-M3</a></li></ul>
+ <ul><li><a href="#Fixed_in_Apache_Tomcat_11.0.27">Fixed in Apache Tomcat
11.0.27</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.26">Fixed in Apache
Tomcat 11.0.26</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.25">Fixed in
Apache Tomcat 11.0.25</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.24">Fixed in Apache Tomcat
11.0.24</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.23">Fixed in Apache
Tomcat 11.0.23</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.22">Fixed in
Apache Tomcat 11.0.22</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.21">Fixed in Apache Tomcat
11.0.21</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.20">Fixed in Apache
Tomcat 11.0.20</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.18">Fixed in
Apache Tomcat 11.0.18</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.15">Fixed in Apache Tomcat
11.0.15</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.12">Fixed in Apache
Tomcat 11.0.12</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.11">Fixed in
Apache Tomcat 11.0.11</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.10">Fixed in Apache Tomcat
11.0.10</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.9">Fixed in Apache
Tomcat 11.0.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.8">Fixed in
Apache Tomcat 11.0.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.7">Fixed
in Apache Tomcat 11.0.7</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.6">Fixed in Apache Tomcat
11.0.6</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.5">Fixed in Apache
Tomcat 11.0.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.3">Fixed in
Apache Tomcat 11.0.3</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.2">Fixed
in Apache Tomcat 11.0.2</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.1">Fixed in Apache Tomcat
11.0.1</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0">Fixed in Apache
Tomcat 11.0.0</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M21">Fixed in
Apache Tomcat 11.0.0-M21</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0
-M17">Fixed in Apache Tomcat 11.0.0-M17</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M12">Fixed in Apache Tomcat
11.0.0-M12</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M11">Fixed in
Apache Tomcat 11.0.0-M11</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M6">Fixed in Apache Tomcat
11.0.0-M6</a></li><li><a href="#Fixed_in_Apache_Tomcat_11.0.0-M5">Fixed in
Apache Tomcat 11.0.0-M5</a></li><li><a
href="#Fixed_in_Apache_Tomcat_11.0.0-M3">Fixed in Apache Tomcat
11.0.0-M3</a></li></ul>
+ </div><h3 id="Fixed_in_Apache_Tomcat_11.0.27"><span
class="pull-right">2026-10-12</span> Fixed in Apache Tomcat 11.0.27</h3><div
class="text">
+
+ <p><strong>Important: AJP response mix-up</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-103119"
rel="nofollow">CVE-2026-103119</a></p>
+
+ <p>A buffer under-read meant that a large non-blocking write could result
in
+ the response body being split between the current request and the next
+ request received on that connection leading most likely to failure of
the
+ second request and possibly leakage of data from the first response to
the
+ second.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/f13748baa17a5e28925be455e0e2832e2032f58c">f13748ba</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M25 to 11.0.26</p>
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101356"
rel="nofollow">CVE-2026-101356</a></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/1dc6aa151b3b99b32ac9ae7c60e41c326063321b">1dc6aa15</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.22 to 11.0.26</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101296"
rel="nofollow">CVE-2026-101296</a></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/e43453fc04abb44f64faf571ca98af71aa3c20a1">e43453fc</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.26</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-93446"
rel="nofollow">CVE-2026-93446</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/e49e0c47ea925ad9442ba933a144ea62433d6a06">e49e0c47</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M21 to 11.0.26</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88041"
rel="nofollow">CVE-2026-88041</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/a276dea827437090498678e09df0539ec397a7b5">a276dea8</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M23 to 11.0.26</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74049"
rel="nofollow">CVE-2026-74049</a></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/d7948a090ad3f803d9669c8b8401c39e2f532bb7">d7948a09</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.26</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74048"
rel="nofollow">CVE-2026-74048</a></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/db6d674b40ac572f3b2205a4c4f06836516fd3f5">db6d674b</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M14 to 11.0.26</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_11.0.26"><span
class="pull-right">2026-09-15</span> Fixed in Apache Tomcat 11.0.26</h3><div
class="text">
<p><strong>Low: WebSocket message smuggling with
Modified: tomcat/site/trunk/docs/security-9.html
==============================================================================
--- tomcat/site/trunk/docs/security-9.html Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/docs/security-9.html Tue Oct 20 13:27:49 2026
(r1939289)
@@ -36,7 +36,117 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><li><a href="#Fixed_in_Apache_Tomcat_9.0.122">Fixed in Apache Tomcat
9.0.122</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.121">Fixed in Apache
Tomcat 9.0.121</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.120">Fixed in
Apache Tomcat 9.0.120</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.119">Fixed in Apache Tomcat
9.0.119</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.118">Fixed in Apache
Tomcat 9.0.118</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.117">Fixed in
Apache Tomcat 9.0.117</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.116">Fixed in Apache Tomcat
9.0.116</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.115">Fixed in Apache
Tomcat 9.0.115</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.113">Fixed in
Apache Tomcat 9.0.113</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.110">Fixed in Apache Tomcat
9.0.110</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.109">Fixed in Apache
Tomcat 9.0.109</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.108">Fixed in
Apache Tomcat 9.0.108</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.107">Fixed in Apache Tomcat
9.0.107</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.106">Fixed in Apache
Tomcat 9.0.106</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.105">Fixed in
Apache Tomcat 9.0.105</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.104">Fixed in Apache Tomcat
9.0.104</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.102">Fixed in Apache
Tomcat 9.0.102</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.99">Fixed in
Apache Tomcat 9.0.99</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.98">Fixed
in Apache Tomcat 9.0.98</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.97">Fixed in Apache Tomcat
9.0.97</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.96">Fixed in Apache
Tomcat 9.0.96</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.90">Fixed in
Apache Tomcat 9.0.90</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.86">Fixed
in Apache Tomcat 9.0.86</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.83
">Fixed in Apache Tomcat 9.0.83</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.81">Fixed in Apache Tomcat
9.0.81</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.80">Fixed in Apache
Tomcat 9.0.80</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.75">Fixed in
Apache Tomcat 9.0.75</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.74">Fixed
in Apache Tomcat 9.0.74</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.72">Fixed in Apache Tomcat
9.0.72</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.71">Fixed in Apache
Tomcat 9.0.71</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.69">Fixed in
Apache Tomcat 9.0.69</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.68">Fixed
in Apache Tomcat 9.0.68</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.65">Fixed in Apache Tomcat
9.0.65</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.63">Fixed in Apache
Tomcat 9.0.63</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.62">Fixed in
Apache Tomcat 9.0.62</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.58"
>Fixed in Apache Tomcat 9.0.58</a></li><li><a
>href="#Fixed_in_Apache_Tomcat_9.0.54">Fixed in Apache Tomcat
>9.0.54</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.48">Fixed in Apache
>Tomcat 9.0.48</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.46">Fixed in
>Apache Tomcat 9.0.46</a></li><li><a
>href="#Fixed_in_Apache_Tomcat_9.0.45">Fixed in Apache Tomcat
>9.0.45</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.44">Fixed in Apache
>Tomcat 9.0.44</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.43">Fixed in
>Apache Tomcat 9.0.43</a></li><li><a
>href="#Fixed_in_Apache_Tomcat_9.0.40">Fixed in Apache Tomcat
>9.0.40</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.38">Fixed in Apache
>Tomcat 9.0.38</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.37">Fixed in
>Apache Tomcat 9.0.37</a></li><li><a
>href="#Fixed_in_Apache_Tomcat_9.0.36">Fixed in Apache Tomcat
>9.0.36</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.35">Fixed in Apache
>Tomcat 9.0.35</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.31">
Fixed in Apache Tomcat 9.0.31</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.30">Fixed in Apache Tomcat
9.0.30</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.29">Fixed in Apache
Tomcat 9.0.29</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.21">Fixed in
Apache Tomcat 9.0.21</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.20">Fixed
in Apache Tomcat 9.0.20</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.19">Fixed in Apache Tomcat
9.0.19</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.16">Fixed in Apache
Tomcat 9.0.16</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.12">Fixed in
Apache Tomcat 9.0.12</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.10">Fixed
in Apache Tomcat 9.0.10</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.9">Fixed in Apache Tomcat
9.0.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.8">Fixed in Apache
Tomcat 9.0.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.5">Fixed in
Apache Tomcat 9.0.5</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.2">Fixed in
Apache Tomcat 9.0.2</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.1">Fixed
in Apache Tomcat 9.0.1</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M22">Fixed in Apache Tomcat
9.0.0.M22</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M21">Fixed in
Apache Tomcat 9.0.0.M21</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M19">Fixed in Apache Tomcat
9.0.0.M19</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M18">Fixed in
Apache Tomcat 9.0.0.M18</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M17">Fixed in Apache Tomcat
9.0.0.M17</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M15">Fixed in
Apache Tomcat 9.0.0.M15</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M13">Fixed in Apache Tomcat
9.0.0.M13</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M10">Fixed in
Apache Tomcat 9.0.0.M10</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M8">Fixed in Apache Tomcat
9.0.0.M8</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M3">Fixed in Apache
Tomcat 9.0.0.M3</a></li><
li><a href="#Not_a_vulnerability_in_Tomcat">Not a vulnerability in
Tomcat</a></li></ul>
+ <ul><li><a href="#Fixed_in_Apache_Tomcat_9.0.123">Fixed in Apache Tomcat
9.0.123</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.122">Fixed in Apache
Tomcat 9.0.122</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.121">Fixed in
Apache Tomcat 9.0.121</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.120">Fixed in Apache Tomcat
9.0.120</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.119">Fixed in Apache
Tomcat 9.0.119</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.118">Fixed in
Apache Tomcat 9.0.118</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.117">Fixed in Apache Tomcat
9.0.117</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.116">Fixed in Apache
Tomcat 9.0.116</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.115">Fixed in
Apache Tomcat 9.0.115</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.113">Fixed in Apache Tomcat
9.0.113</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.110">Fixed in Apache
Tomcat 9.0.110</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.109">Fixed in
Apache Tomcat 9.0.109</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.108">Fixed in Apache Tomcat
9.0.108</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.107">Fixed in Apache
Tomcat 9.0.107</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.106">Fixed in
Apache Tomcat 9.0.106</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.105">Fixed in Apache Tomcat
9.0.105</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.104">Fixed in Apache
Tomcat 9.0.104</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.102">Fixed in
Apache Tomcat 9.0.102</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.99">Fixed in Apache Tomcat
9.0.99</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.98">Fixed in Apache
Tomcat 9.0.98</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.97">Fixed in
Apache Tomcat 9.0.97</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.96">Fixed
in Apache Tomcat 9.0.96</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.90">Fixed in Apache Tomcat
9.0.90</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.
86">Fixed in Apache Tomcat 9.0.86</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.83">Fixed in Apache Tomcat
9.0.83</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.81">Fixed in Apache
Tomcat 9.0.81</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.80">Fixed in
Apache Tomcat 9.0.80</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.75">Fixed
in Apache Tomcat 9.0.75</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.74">Fixed in Apache Tomcat
9.0.74</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.72">Fixed in Apache
Tomcat 9.0.72</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.71">Fixed in
Apache Tomcat 9.0.71</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.69">Fixed
in Apache Tomcat 9.0.69</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.68">Fixed in Apache Tomcat
9.0.68</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.65">Fixed in Apache
Tomcat 9.0.65</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.63">Fixed in
Apache Tomcat 9.0.63</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.6
2">Fixed in Apache Tomcat 9.0.62</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.58">Fixed in Apache Tomcat
9.0.58</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.54">Fixed in Apache
Tomcat 9.0.54</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.48">Fixed in
Apache Tomcat 9.0.48</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.46">Fixed
in Apache Tomcat 9.0.46</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.45">Fixed in Apache Tomcat
9.0.45</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.44">Fixed in Apache
Tomcat 9.0.44</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.43">Fixed in
Apache Tomcat 9.0.43</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.40">Fixed
in Apache Tomcat 9.0.40</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.38">Fixed in Apache Tomcat
9.0.38</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.37">Fixed in Apache
Tomcat 9.0.37</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.36">Fixed in
Apache Tomcat 9.0.36</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.35
">Fixed in Apache Tomcat 9.0.35</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.31">Fixed in Apache Tomcat
9.0.31</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.30">Fixed in Apache
Tomcat 9.0.30</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.29">Fixed in
Apache Tomcat 9.0.29</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.21">Fixed
in Apache Tomcat 9.0.21</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.20">Fixed in Apache Tomcat
9.0.20</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.19">Fixed in Apache
Tomcat 9.0.19</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.16">Fixed in
Apache Tomcat 9.0.16</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.12">Fixed
in Apache Tomcat 9.0.12</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.10">Fixed in Apache Tomcat
9.0.10</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.9">Fixed in Apache
Tomcat 9.0.9</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.8">Fixed in
Apache Tomcat 9.0.8</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.5">Fixe
d in Apache Tomcat 9.0.5</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.2">Fixed in Apache Tomcat
9.0.2</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.1">Fixed in Apache
Tomcat 9.0.1</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M22">Fixed in
Apache Tomcat 9.0.0.M22</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M21">Fixed in Apache Tomcat
9.0.0.M21</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M19">Fixed in
Apache Tomcat 9.0.0.M19</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M18">Fixed in Apache Tomcat
9.0.0.M18</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M17">Fixed in
Apache Tomcat 9.0.0.M17</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M15">Fixed in Apache Tomcat
9.0.0.M15</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M13">Fixed in
Apache Tomcat 9.0.0.M13</a></li><li><a
href="#Fixed_in_Apache_Tomcat_9.0.0.M10">Fixed in Apache Tomcat
9.0.0.M10</a></li><li><a href="#Fixed_in_Apache_Tomcat_9.0.0.M8">Fixed in
Apache Tomcat 9.0.0.M8</a></li><li
><a href="#Fixed_in_Apache_Tomcat_9.0.0.M3">Fixed in Apache Tomcat
>9.0.0.M3</a></li><li><a href="#Not_a_vulnerability_in_Tomcat">Not a
>vulnerability in Tomcat</a></li></ul>
+ </div><h3 id="Fixed_in_Apache_Tomcat_9.0.123"><span
class="pull-right">2026-10-12</span> Fixed in Apache Tomcat 9.0.123</h3><div
class="text">
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101356"
rel="nofollow">CVE-2026-101356</a></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/4b1eb9a1664b10471f5740279d9f2e2259c5d108">4b1eb9a1</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.118 to 9.0.122</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101296"
rel="nofollow">CVE-2026-101296</a></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/42827afa4d073ac3d9f8b3cc81b857aa455bf1e6">42827afa</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.122</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-93446"
rel="nofollow">CVE-2026-93446</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/02166d1c7c32973685734ef132e56eb232605cc5">02166d1c</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.90 to 9.0.122</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88041"
rel="nofollow">CVE-2026-88041</a></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/885985272887e9a5d47245cec240a5d1d0e39b5b">88598527</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.92 to 9.0.122</p>
+
+ <p><strong>Low: TOCTOU when setting specific permissions for Unix Domain
+ Sockets - Fix for CVE-2026-65183 did not address APR connector</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-80353"
rel="nofollow">CVE-2026-80353</a></p>
+
+ <p>A race condition when creating a Unix Domain Socket allowed an
+ unauthorised local user to access the Unix Domain Socket.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/894158fd49679a6bd48d9689905829e1fdc45cb2">894158fd</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 26 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.47 to 9.0.122</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74049"
rel="nofollow">CVE-2026-74049</a></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/6cd2ec7f60b13f8bd93290993401958502c33211">6cd2ec7f</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.122</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-74048"
rel="nofollow">CVE-2026-74048</a></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/25714916ca36205f63f3c3d0da419981ed9d83c2">25714916</a>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.92 to 9.0.122</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_9.0.122"><span
class="pull-right">2026-09-15</span> Fixed in Apache Tomcat 9.0.122</h3><div
class="text">
<p><strong>Low: WebSocket message smuggling with
Modified: tomcat/site/trunk/xdocs/security-10.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-10.xml Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/xdocs/security-10.xml Tue Oct 20 13:27:49 2026
(r1939289)
@@ -56,6 +56,103 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 10.1.61" rtext="2026-10-12">
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <cve>CVE-2026-101356</cve></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="6c7da60893bd186d6cb2df7330299d7e70e68279"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.55 to 10.1.60</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <cve>CVE-2026-101296</cve></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="8fafc6f263311b7a0b7ce67477822175d1adf7ce"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.60</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <cve>CVE-2026-93446</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="ccbe01a52a9b255ad98e71b5bed76ed10a099503"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.25 to 10.1.60</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <cve>CVE-2026-88041</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="395bcafcfcf2e1cff451a5785361679931b49a79"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.27 to 10.1.60</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <cve>CVE-2026-74049</cve></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="f8023d833675f00968b89b45639210d3c7dcc95d"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.60</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <cve>CVE-2026-74048</cve></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="5561032ca9d2bf32fafd8a8a417692c9826e30fe"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 10.1.22 to 10.1.60</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 10.1.60" rtext="2026-09-15">
<p><strong>Low: WebSocket message smuggling with
Modified: tomcat/site/trunk/xdocs/security-11.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-11.xml Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/xdocs/security-11.xml Tue Oct 20 13:27:49 2026
(r1939289)
@@ -50,6 +50,120 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 11.0.27" rtext="2026-10-12">
+
+ <p><strong>Important: AJP response mix-up</strong>
+ <cve>CVE-2026-103119</cve></p>
+
+ <p>A buffer under-read meant that a large non-blocking write could result
in
+ the response body being split between the current request and the next
+ request received on that connection leading most likely to failure of
the
+ second request and possibly leakage of data from the first response to
the
+ second.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="f13748baa17a5e28925be455e0e2832e2032f58c"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M25 to 11.0.26</p>
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <cve>CVE-2026-101356</cve></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="1dc6aa151b3b99b32ac9ae7c60e41c326063321b"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.22 to 11.0.26</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <cve>CVE-2026-101296</cve></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="e43453fc04abb44f64faf571ca98af71aa3c20a1"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.26</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <cve>CVE-2026-93446</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="e49e0c47ea925ad9442ba933a144ea62433d6a06"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M21 to 11.0.26</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <cve>CVE-2026-88041</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="a276dea827437090498678e09df0539ec397a7b5"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M23 to 11.0.26</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <cve>CVE-2026-74049</cve></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="d7948a090ad3f803d9669c8b8401c39e2f532bb7"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.26</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <cve>CVE-2026-74048</cve></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="db6d674b40ac572f3b2205a4c4f06836516fd3f5"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 11.0.0-M14 to 11.0.26</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 11.0.26" rtext="2026-09-15">
<p><strong>Low: WebSocket message smuggling with
Modified: tomcat/site/trunk/xdocs/security-9.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-9.xml Tue Oct 20 12:45:04 2026
(r1939288)
+++ tomcat/site/trunk/xdocs/security-9.xml Tue Oct 20 13:27:49 2026
(r1939289)
@@ -50,6 +50,118 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 9.0.123" rtext="2026-10-12">
+
+ <p><strong>Important: HTTP/2 request/response mix-up after error during
+ async processing</strong>
+ <cve>CVE-2026-101356</cve></p>
+
+ <p>Incorrect object recycling and re-use affecting HTTP/2 processing of
+ asynchronous servlets can trigger request and/or response mix-up between
+ users.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="4b1eb9a1664b10471f5740279d9f2e2259c5d108"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 16 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.118 to 9.0.122</p>
+
+ <p><strong>Important: JNDIRealm bind credential validation fails open for
+ non-GSSAPI SASL mechanisms</strong>
+ <cve>CVE-2026-101296</cve></p>
+
+ <p>A missing critical step in authentication vulnerability in Apache Tomcat
+ when the JNDI realm was configured with with a non GSSAPI SASL
+ authentication mechanism allowed attackers to authenticate without
+ providing the correct password.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="42827afa4d073ac3d9f8b3cc81b857aa455bf1e6"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 14 September
2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.122</p>
+
+ <p><strong>Low: Possible TLS 1.3 connection failures</strong>
+ <cve>CVE-2026-93446</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3
+ connections to fail intermittently.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="02166d1c7c32973685734ef132e56eb232605cc5"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 9 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.90 to 9.0.122</p>
+
+ <p><strong>Low: HTTP/2 trailer header cross-contamination</strong>
+ <cve>CVE-2026-88041</cve></p>
+
+ <p>Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer
+ information from a previous request to leak into a subsequent
+ request.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="885985272887e9a5d47245cec240a5d1d0e39b5b"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 7 September 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.92 to 9.0.122</p>
+
+ <p><strong>Low: TOCTOU when setting specific permissions for Unix Domain
+ Sockets - Fix for CVE-2026-65183 did not address APR connector</strong>
+ <cve>CVE-2026-80353</cve></p>
+
+ <p>A race condition when creating a Unix Domain Socket allowed an
+ unauthorised local user to access the Unix Domain Socket.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="894158fd49679a6bd48d9689905829e1fdc45cb2"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 26 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.47 to 9.0.122</p>
+
+ <p><strong>Low: Jasper JSTL <c:redirect> plug-in implementation omits
+ page abort (SKIP_PAGE)</strong>
+ <cve>CVE-2026-74049</cve></p>
+
+ <p>The Jasper JSTL plug-in replacement for the <c:redirect> does not
+ immediately end processing, allowing the rest of the page to be
processed
+ despite the redirect.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="6cd2ec7f60b13f8bd93290993401958502c33211"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.122</p>
+
+ <p><strong>Low: OpenSSL-FFM FIPS failure does not prevent start-up</strong>
+ <cve>CVE-2026-74048</cve></p>
+
+ <p>If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS
+ activation fails, Tomcat logs and error but continues to use JSSE in
+ non-FIPS mode with the provided configuration.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="25714916ca36205f63f3c3d0da419981ed9d83c2"/>.</p>
+
+ <p>This issue was reported to the Tomcat security team on 13 August 2026.
+ The issue was made public on 20 October 2026.</p>
+
+ <p>Affects: 9.0.92 to 9.0.122</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 9.0.122" rtext="2026-09-15">
<p><strong>Low: WebSocket message smuggling with
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]