Source: tomcat11 X-Debbugs-CC: [email protected] Severity: grave Tags: security
Hi, The following vulnerabilities were published for tomcat11. CVE-2026-106012[0]: | Incorrect Authorization vulnerability in Apache Tomcat could occur | during a request dispatch if the request depended on a security- | role-ref provided by the dispatch target. This issue affects | Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 | through 10.1.61, from 9.0.0.M1 through 9.0.123. The following | versions were EOL at the time the CVE was created but are known to | be affected: from 8.5.0 through 8.5.100, from 7.0.0 through | 7.0.109. Other unsupported versions may also be affected. Users | are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, | which fixes the issue. Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/4d829c560fa0945c93c8b63da83849879a332962 (11.0.28) CVE-2026-116830[1]: | Missing release of resource after effective lifetime vulnerability | in Apache Tomcat's HTTP/2 initial connection handling leads to DoS. | This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, | from 10.1.0-M1 through 10.1.61, from 9.0.20 through 9.0.123. | Users are recommended to upgrade to version 11.0.29, 10.1.62 or | 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/b74fa31d0b8da208aec3abf37f6424df2a607ad1 (11.0.28) CVE-2026-121649[2]: | Use of cache containing sensitive information vulnerability in | Apache Tomcat's ExpiresFilter caused by the filter removing cache- | control header fields set by the authentication layer. This issue | affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from | 10.1.0-M1 through 10.1.61, from 9.0.0.M1 through 9.0.123. The | following versions were EOL at the time the CVE was created but are | known to be affected: from 8.5.0 through 8.5.100, from 7.0.1 through | 7.0.109. Older unsupported versions may also be affected. Users | are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, | which fix the issue. Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/069d34eedc19ac596f05dcde52b07b131e5f27ab (11.0.28) CVE-2026-133325[3]: | Key exchange without entity authentication vulnerability in Apache | Tomcat allowed an unauthenticated node to join a cluster when the | cluster was secured with TLS 1.3 and TLS-PSK. This issue affects | Apache Tomcat: 11.0.29, 10.1.62, 9.0.124. Users are recommended | to switch to TLS 1.2 and PLDS-PSK or upgrade to version 11.0.30, | 10.1.63 or 9.0.123 (when released), which fix the issue. https://github.com/apache/tomcat/commit/2e6c85ba0937f3dc9877dadd433167fcd45f8dbc (11.x) CVE-2026-118436[4]: | Allocation of resources without limits or throttling vulnerability | in Apache Tomcat in the CGI Servlet when handling POST bodies can | result in a DoS for some inputs. This issue affects Apache | Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through | 10.1.61, from 9.0.0.M1 through 9.0.123. The following versions | were EOL at the time the CVE was created but are known to be | affected: from 8.5.0 through 8.5.100, from 7.0.0 through | 7.0.109. Other unsupported versions may also be affected. Users | are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, | which fix the issue. Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/653bfad0f7f5407b7757d1c4dd6eda46973b3ca0 (11.0.28) CVE-2026-118028[5]: | Execution After Redirect (EAR) vulnerability in Apache Tomcat in | RedirectValve affecting flags [F], [G] and [R]. This issue | affects Apache Tomcat: from 11.0.0-M18 through 11.0.27, from 10.1.20 | through 10.1.61, from 9.0.87 through 9.0.123. The following | versions were EOL at the time the CVE was created but are known to | be affected: 8.5.100. Other unsupported versions may also be | affected. Users are recommended to upgrade to version 11.0.29, | 10.1.62, 9.0.124, which fixes the issue. Note: Tomcat 11.0.28 was | not released https://github.com/apache/tomcat/commit/b756a2b1683a78af316404970c56e7e68a29f321 (11.0.28) CVE-2026-118233[6]: | Allocation of resources without limits or throttling vulnerability | in Apache Tomcat during HTTP upgrade in some circumstances lead to | possible DoS. This issue affects Apache Tomcat: from 11.0.0-M1 | through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.41 through | 9.0.123. The following versions were EOL at the time the CVE was | created but are known to be affected: from 8.5.61 through | 8.5.100. Other unsupported versions may also be affected. Users | are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, | which fix the issue. Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/ae34e37285852f98c82dab1ee4edec23bdd7c673 (11.0.28) CVE-2026-117517[7]: | The fix for CVE-2026-25854 was incomplete. This issue affects | Apache Tomcat: from 11.0.19 through 11.0.27, from 10.1.53 through | 10.1.61, from 9.0.116 through 9.0.123. Users are recommended to | upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue. | Note: Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/cf7eae399468ae0e8f190dc3022e03028fa20314 (11.0.28) CVE-2026-116561[8]: | Improper cleanup on thrown exception vulnerability in Apache Tomcat | meant that an HTTP 200 response was sent rather than an HTTP 500 | response after a AuthException was thrown during Jakarta | Authentication secureResponse(). This issue affects Apache | Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through | 10.1.61, from 9.0.0.M1 through 9.0.123. The following versions | were EOL at the time the CVE was created but are known to be | affected: from 8.5.0 through 8.5.100. Other unsupported versions may | also be affected. Users are recommended to upgrade to version | 11.0.29, 10.0.62 or 9.0.124, which fix the issue. Note: Tomcat | 11.0.28 was not released https://github.com/apache/tomcat/commit/17ca7505d29257d47eda998c28aa0b4b2ac117c6 (11.0.28) CVE-2026-116600[9]: | Missing release of memory after effective lifetime vulnerability in | Apache Tomcat via WebSocket. This issue affects Apache Tomcat: | from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from | 9.0.22 through 9.0.123 The following versions were EOL at the | time the CVE was created but are known to be affected: from 8.5.0 | through 8.5.100, from 7.0.43 through 7.0.109. Other unsupported | versions may also be affected. Users are recommended to upgrade | to version 11.0.29, 10.0.62 or 9.0.124, which fix the issue. Note: | Tomcat 11.0.28 was not released https://github.com/apache/tomcat/commit/fc0dbcd7df8e719c7528998e4c15cd94239c8afd (11.0.28) CVE-2026-95517[10]: | Reliance on obfuscation or encryption of Security-Relevant inputs | without integrity checking, Improper validation of integrity check | value, Cleartext transmission of sensitive information vulnerability | in the EncryptInterceptor of Apache Tomcat. This issue affects | Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 | through 10.1.61, from 9.0.13 through 9.0.123. The following | versions were EOL at the time the CVE was created but are known to | be affected: from 8.5.38 through 8.5.100, from 7.0.100 through | 7.0.109. Other unsupported versions may also be affected. Users | are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124 | and switch to TLS-PSK to encrypt cluster communication, which fixes | the issue. Note: Tomcat 11.0.28 was not released If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-106012 https://www.cve.org/CVERecord?id=CVE-2026-106012 [1] https://security-tracker.debian.org/tracker/CVE-2026-116830 https://www.cve.org/CVERecord?id=CVE-2026-116830 [2] https://security-tracker.debian.org/tracker/CVE-2026-121649 https://www.cve.org/CVERecord?id=CVE-2026-121649 [3] https://security-tracker.debian.org/tracker/CVE-2026-133325 https://www.cve.org/CVERecord?id=CVE-2026-133325 [4] https://security-tracker.debian.org/tracker/CVE-2026-118436 https://www.cve.org/CVERecord?id=CVE-2026-118436 [5] https://security-tracker.debian.org/tracker/CVE-2026-118028 https://www.cve.org/CVERecord?id=CVE-2026-118028 [6] https://security-tracker.debian.org/tracker/CVE-2026-118233 https://www.cve.org/CVERecord?id=CVE-2026-118233 [7] https://security-tracker.debian.org/tracker/CVE-2026-117517 https://www.cve.org/CVERecord?id=CVE-2026-117517 [8] https://security-tracker.debian.org/tracker/CVE-2026-116561 https://www.cve.org/CVERecord?id=CVE-2026-116561 [9] https://security-tracker.debian.org/tracker/CVE-2026-116600 https://www.cve.org/CVERecord?id=CVE-2026-116600 [10] https://security-tracker.debian.org/tracker/CVE-2026-95517 https://www.cve.org/CVERecord?id=CVE-2026-95517 Please adjust the affected versions in the BTS as needed.

