Author: markt
Date: Mon Oct 27 17:12:06 2025
New Revision: 1929379
Log:
Add details for CVE-2025-55752, CVEW-2025-55754 and CVE-2025-61795
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 Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/docs/security-10.html Mon Oct 27 17:12:06 2025
(r1929379)
@@ -42,7 +42,72 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><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.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_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 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.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.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_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.2
3">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>
+ </div><h3 id="Fixed_in_Apache_Tomcat_10.1.47"><span
class="pull-right">2025-10-07</span> Fixed in Apache Tomcat 10.1.47</h3><div
class="text">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61795";
rel="nofollow">CVE-2025-61795</a></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ disc were not cleaned up immediately but left for the garbage collection
+ process to delete. Depending on JVM settings, application memory usage
+ and application load, it was possible that space for the temporary
copies
+ of uploaded parts would be filled faster than GC cleared it, leading to
a
+ DoS.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/af6e9181620304c0d818121c29c074e1330610d0";>af6e9181</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.46</p>
+
+ </div><h3 id="Fixed_in_Apache_Tomcat_10.1.45"><span
class="pull-right">2025-09-08</span> Fixed in Apache Tomcat 10.1.45</h3><div
class="text">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55754";
rel="nofollow">CVE-2025-55754</a></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clip-board and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/138d7f5cfaae683078948303333c080e6faa75d2";>138d7f5c</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.44</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55752";
rel="nofollow">CVE-2025-55752</a></p>
+
+ <p>The fix for bug <a
href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60013";>60013</a>
introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/130d36d8492ef9e4eb22952c17c92423cb35fd06";>130d36d8</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.44</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_10.1.44"><span
class="pull-right">2025-08-07</span> Fixed in Apache Tomcat 10.1.44</h3><div
class="text">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
Modified: tomcat/site/trunk/docs/security-11.html
==============================================================================
--- tomcat/site/trunk/docs/security-11.html Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/docs/security-11.html Mon Oct 27 17:12:06 2025
(r1929379)
@@ -36,7 +36,72 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><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.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.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.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 Tomca
t 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.12"><span
class="pull-right">2025-10-07</span> Fixed in Apache Tomcat 11.0.12</h3><div
class="text">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61795";
rel="nofollow">CVE-2025-61795</a></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ disc were not cleaned up immediately but left for the garbage collection
+ process to delete. Depending on JVM settings, application memory usage
+ and application load, it was possible that space for the temporary
copies
+ of uploaded parts would be filled faster than GC cleared it, leading to
a
+ DoS.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/1cdf5f730ede75a0759492f179ac21ca4ff68e06";>1cdf5f73</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.11</p>
+
+ </div><h3 id="Fixed_in_Apache_Tomcat_11.0.11"><span
class="pull-right">2025-09-05</span> Fixed in Apache Tomcat 11.0.11</h3><div
class="text">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55754";
rel="nofollow">CVE-2025-55754</a></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clip-board and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/5a3db092982c0c58d4855304167ee757fe5e79bb";>5a3db092</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.10</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55752";
rel="nofollow">CVE-2025-55752</a></p>
+
+ <p>The fix for bug <a
href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60013";>60013</a>
introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/fec06c610ed7466b401e29cc567a58aee5ed826a";>fec06c61</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.10</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_11.0.10"><span
class="pull-right">2025-08-06</span> Fixed in Apache Tomcat 11.0.10</h3><div
class="text">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
Modified: tomcat/site/trunk/docs/security-9.html
==============================================================================
--- tomcat/site/trunk/docs/security-9.html Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/docs/security-9.html Mon Oct 27 17:12:06 2025
(r1929379)
@@ -36,7 +36,72 @@
</p>
</div><h3 id="Table_of_Contents">Table of Contents</h3><div class="text">
- <ul><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.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 Tomca
t 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_vuln
erability_in_Tomcat">Not a vulnerability in Tomcat</a></li></ul>
+ <ul><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.1.109">Fixed in Apache
Tomcat 9.1.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.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 T
omcat 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 To
mcat 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 Tom
cat 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_Apach
e_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.110"><span
class="pull-right">2025-10-06</span> Fixed in Apache Tomcat 9.0.110</h3><div
class="text">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61795";
rel="nofollow">CVE-2025-61795</a></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ disc were not cleaned up immediately but left for the garbage collection
+ process to delete. Depending on JVM settings, application memory usage
+ and application load, it was possible that space for the temporary
copies
+ of uploaded parts would be filled faster than GC cleared it, leading to
a
+ DoS.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/afa422bd7ca1eef0f507259c682fd876494d9c3b";>afa422bd</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.109</p>
+
+ </div><h3 id="Fixed_in_Apache_Tomcat_9.1.109"><span
class="pull-right">2025-09-05</span> Fixed in Apache Tomcat 9.1.109</h3><div
class="text">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55754";
rel="nofollow">CVE-2025-55754</a></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clip-board and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/a03cabf3a36a42d27d8d997ed31f034f50ba6cd5";>a03cabf3</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.40 to 9.0.108</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55752";
rel="nofollow">CVE-2025-55752</a></p>
+
+ <p>The fix for bug <a
href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60013";>60013</a>
introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <a
href="https://github.com/apache/tomcat/commit/b5042622b8b78340ae65403c55dcb9c7416924df";>b5042622</a>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.0.M11 to 9.0.108</p>
+
</div><h3 id="Fixed_in_Apache_Tomcat_9.0.108"><span
class="pull-right">2025-08-06</span> Fixed in Apache Tomcat 9.0.108</h3><div
class="text">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
Modified: tomcat/site/trunk/xdocs/security-10.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-10.xml Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/xdocs/security-10.xml Mon Oct 27 17:12:06 2025
(r1929379)
@@ -56,6 +56,75 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 10.1.47" rtext="2025-10-07">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <cve>CVE-2025-61795</cve></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ local storage were not cleaned up immediately but left for the garbage
+ collection process to delete. Depending on JVM settings, application
+ memory usage and application load, it was possible that space for the
+ temporary copies of uploaded parts would be filled faster than GC
cleared
+ it, leading to a DoS.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="af6e9181620304c0d818121c29c074e1330610d0"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.46</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 10.1.45" rtext="2025-09-08">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <cve>CVE-2025-55754</cve></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clipboard and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="138d7f5cfaae683078948303333c080e6faa75d2"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.44</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <cve>CVE-2025-55752</cve></p>
+
+ <p>The fix for bug <bug>60013</bug> introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="130d36d8492ef9e4eb22952c17c92423cb35fd06"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 10.1.0-M1 to 10.1.44</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 10.1.44" rtext="2025-08-07">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
Modified: tomcat/site/trunk/xdocs/security-11.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-11.xml Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/xdocs/security-11.xml Mon Oct 27 17:12:06 2025
(r1929379)
@@ -50,6 +50,75 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 11.0.12" rtext="2025-10-07">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <cve>CVE-2025-61795</cve></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ local storage were not cleaned up immediately but left for the garbage
+ collection process to delete. Depending on JVM settings, application
+ memory usage and application load, it was possible that space for the
+ temporary copies of uploaded parts would be filled faster than GC
cleared
+ it, leading to a DoS.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="1cdf5f730ede75a0759492f179ac21ca4ff68e06"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.11</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 11.0.11" rtext="2025-09-05">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <cve>CVE-2025-55754</cve></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clipboard and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="5a3db092982c0c58d4855304167ee757fe5e79bb"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.10</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <cve>CVE-2025-55752</cve></p>
+
+ <p>The fix for bug <bug>60013</bug> introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="fec06c610ed7466b401e29cc567a58aee5ed826a"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 11.0.0-M1 to 11.0.10</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 11.0.10" rtext="2025-08-06">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
Modified: tomcat/site/trunk/xdocs/security-9.xml
==============================================================================
--- tomcat/site/trunk/xdocs/security-9.xml Mon Oct 27 15:54:16 2025
(r1929378)
+++ tomcat/site/trunk/xdocs/security-9.xml Mon Oct 27 17:12:06 2025
(r1929379)
@@ -50,6 +50,75 @@
<toc/>
</section>
+ <section name="Fixed in Apache Tomcat 9.0.110" rtext="2025-10-06">
+
+ <p><strong>Low: Delayed cleaning of multipart upload temporary files may
+ lead to DoS</strong>
+ <cve>CVE-2025-61795</cve></p>
+
+ <p>If an error occurred (including exceeding limits) during the processing
+ of a multipart upload, temporary copies of the uploaded parts written to
+ local storage were not cleaned up immediately but left for the garbage
+ collection process to delete. Depending on JVM settings, application
+ memory usage and application load, it was possible that space for the
+ temporary copies of uploaded parts would be filled faster than GC
cleared
+ it, leading to a DoS.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="afa422bd7ca1eef0f507259c682fd876494d9c3b"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.0.M1 to 9.0.109</p>
+
+ </section>
+
+ <section name="Fixed in Apache Tomcat 9.1.109" rtext="2025-09-05">
+
+ <p><strong>Low: Console manipulation via escape sequences in log
+ messages</strong>
+ <cve>CVE-2025-55754</cve></p>
+
+ <p>Tomcat did not escape ANSI escape sequences in log messages. If Tomcat
+ was running in a console on a Windows operating system, and the console
+ supported ANSI escape sequences, it was possible for an attacker to use
a
+ specially crafted URL to inject ANSI escape sequences to manipulate the
+ console and the clipboard and attempt to trick an administrator into
+ running an attacker controlled command. While no attack vector was
found,
+ it may have been possible to mount this attack on other operating
+ systems.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="a03cabf3a36a42d27d8d997ed31f034f50ba6cd5"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.40 to 9.0.108</p>
+
+ <p><strong>Important: Directory traversal via Rewrite Valve with possible
+ remote code execution if PUT is enabled</strong>
+ <cve>CVE-2025-55752</cve></p>
+
+ <p>The fix for bug <bug>60013</bug> introduced a regression where the
+ rewritten URL was normalized before it was decoded. This introduced the
+ possibility that, for rewrite rules that rewrite query parameters to the
+ URL, an attacker could manipulate the request URI to bypass security
+ constraints including the protection for <code>/WEB-INF/</code> and
+ <code>/META-INF/</code>. If PUT requests were also enabled then
malicious
+ files could be uploaded leading to remote code execution. PUT requests
+ are normally limited to trusted users and it is considered unlikely that
+ PUT requests would be enabled in conjunction with a rewrite that
+ manipulated the URI.</p>
+
+ <p>This was fixed with commit
+ <hashlink hash="b5042622b8b78340ae65403c55dcb9c7416924df"/>.</p>
+
+ <p>The issue was made public on 27 October 2025.</p>
+
+ <p>Affects: 9.0.0.M11 to 9.0.108</p>
+
+ </section>
+
<section name="Fixed in Apache Tomcat 9.0.108" rtext="2025-08-06">
<p><strong>Important: DoS in HTTP/2 due to client triggered stream
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
