<?xml version="1.0" encoding="UTF-8"?>
<document>

  <properties>
    <author>Apache Tomcat Project</author>
    <title>Apache Tomcat 9 vulnerabilities</title>
  </properties>

<body>

  <section name="Apache Tomcat 9.x vulnerabilities">
    <p>This page lists all security vulnerabilities fixed in released versions
       of Apache Tomcat<sup>&#174;</sup> 9.x. Each vulnerability is given a
       <a href="security-impact.html">security impact rating</a> by the Apache
       Tomcat security team &#x2014; please note that this rating may vary from
       platform to platform. We also list the versions of Apache Tomcat the flaw
       is known to affect, and where a flaw has not been verified list the
       version with a question mark.</p>

    <p><strong>Note:</strong> Vulnerabilities that are not Tomcat vulnerabilities
       but have either been incorrectly reported against Tomcat or where Tomcat
       provides a workaround are listed at the end of this page.</p>

    <p>Please note that binary patches are never provided. If you need to
       apply a source code patch, use the building instructions for the
       Apache Tomcat version that you are using. For Tomcat 9.0 those are
       <a href="/tomcat-9.0-doc/building.html"><code>building.html</code></a> and
       <a href="/tomcat-9.0-doc/BUILDING.txt"><code>BUILDING.txt</code></a>.
       Both files can be found in the <code>webapps/docs</code> subdirectory
       of a binary distribution. You may also want to review the
       <a href="/tomcat-9.0-doc/security-howto.html">Security Considerations</a>
       page in the documentation.</p>

    <p>If you need help on building or configuring Tomcat or other help on
       following the instructions to mitigate the known vulnerabilities listed
       here, please send your questions to the public
       <a href="lists.html">Tomcat Users mailing list</a>
    </p>

    <p>If you have encountered an unlisted security vulnerability or other
       unexpected behaviour that has <a href="security-impact.html">security
       impact</a>, or if the descriptions here are incomplete,
       please report them privately to the
       <a href="security.html">Tomcat Security Team</a>. Thank you.
    </p>

  </section>

  <section name="Table of Contents">
    <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 &lt;c:redirect&gt; plug-in implementation omits
       page abort (SKIP_PAGE)</strong>
       <cve>CVE-2026-74049</cve></p>

    <p>The Jasper JSTL plug-in replacement for the &lt;c:redirect&gt; 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
       per-message-deflate</strong>
       <cve>CVE-2026-87022</cve></p>

    <p>Improper handling of length parameter allows WebSocket message smuggling
       when per-message-deflate is used.</p>

    <p>This was fixed with commit
       <hashlink hash="959a52a227cc35101b92dae35b722546167594d6"/>.</p>

    <p>This issue was reported to the Tomcat security team on 7 September 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.121</p>

    <p><strong>Important: Regression in fix for CVE-2026-41293 can trigger
       request header mix-up</strong>
       <cve>CVE-2026-86350</cve></p>

    <p>Inconsistent interpretation of HTTP/2 requests caused by a regression in
       fix for CVE-2026-41293 can trigger request header mix-up.</p>

    <p>This was fixed with commit
       <hashlink hash="5adadc4ef413d5050f664d40800bbff74bd5d5ed"/>.</p>

    <p>This issue was reported to the Tomcat security team on 28 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.118 to 9.0.121</p>

    <p><strong>Moderate: Fix for CVE-2026-34500 was incomplete. OCSP checks
       sometimes soft-fail with FFM even when soft-fail is disabled</strong>
       <cve>CVE-2026-86248</cve></p>

    <p>CLIENT_CERT authentication does not fail as expected for some scenarios
       when OCSP soft fail is disabled.</p>

    <p>This was fixed with commit
       <hashlink hash="fc41d82e0e383e4d6e88ad321d245dafdc17d26d"/>.</p>

    <p>This issue was reported to the Tomcat security team on 28 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.92 to 9.0.121</p>

    <p><strong>Moderate: WebSocket DoS due to lost asynchronous write
       timeout</strong>
       <cve>CVE-2026-79677</cve></p>

    <p>Due to a concurrency bug, an attacker could trigger a denial of service
       as a result of lost time outs for asynchronous WebSocket writes.</p>

    <p>This was fixed with commit
       <hashlink hash="c8fa5430233bca5b209c593dd446f88fda9d543e"/>.</p>

    <p>This issue was reported to the Tomcat security team on 25 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.121</p>

    <p><strong>Low: HTTP/2 DoS via malformed request</strong>
       <cve>CVE-2026-78437</cve></p>

    <p>A malformed HTTP/2 request could potentially (depends on timing) cause
       one request from another user to fail.</p>

    <p>This was fixed with commit
       <hashlink hash="a28c35055ab11d35929ad564beb1a23a67b39546"/>.</p>

    <p>This issue was reported to the Tomcat security team on 24 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.116 to 9.0.121</p>

    <p><strong>Important: AJP DoS via missing request body</strong>
       <cve>CVE-2026-78383</cve></p>

    <p>If the end user did not provide a request body, that could pin an AJP
       processing thread leading to denial of service.</p>

    <p>This was fixed with commit
       <hashlink hash="265bdc0a58b1447ff5d8f8b96ea81de58cb74c8c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 24 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.121</p>

    <p><strong>Important: DoS via busy wait during WebSocket close</strong>
       <cve>CVE-2026-77791</cve></p>

    <p>A busy wait during sending of WebSocket close message enabled a DoS
       attack.</p>

    <p>This was fixed with commit
       <hashlink hash="7a5945f1de1d3310214234dfbbd7c569af52d058"/>.</p>

    <p>This issue was reported to the Tomcat security team on 21 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.74 to 9.0.121</p>

    <p><strong>Low: Stale HPACK emitter injects trailers into recycled pooled
       Request</strong>
       <cve>CVE-2026-77762</cve></p>

    <p>A race condition allowed an attacker to inject trailer fields into
       another HTTP/2 request.</p>

    <p>This was fixed with commit
       <hashlink hash="71f27c2e84810930beda468b5ba732dcd0ef2652"/>.</p>

    <p>This issue was reported to the Tomcat security team on 21 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.39 to 9.0.121</p>

    <p><strong>Low: Transfer-Encoding honored for HTTP/1.0 requests</strong>
       <cve>CVE-2026-77756</cve></p>

    <p>Processing the transfer-encoding header for an HTTP/1.0 request may allow
       an attacker to cause one request from another user to fail when Tomcat is
       located behind a reverse proxy.</p>

    <p>This was fixed with commit
       <hashlink hash="e590588ab7649c93d49b0eb7b3152700a977880d"/>.</p>

    <p>This issue was reported to the Tomcat security team on 20 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.47 to 9.0.121</p>

    <p><strong>Important: Bypass of security constraints for WebSocket
       endpoints</strong>
       <cve>CVE-2026-76183</cve></p>

    <p>Request paths were incorrectly parsed as endpoint templates allowing the
       bypass of security constraints for WebSocket endpoints.</p>

    <p>This was fixed with commit
       <hashlink hash="a93a60a33f4cc202542eb6a0b87b7142d7db311c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 17 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.121</p>

    <p><strong>Low: Cross-context authentication mix-up with Jakarta
       Authentication configured</strong>
       <cve>CVE-2026-75973</cve></p>

    <p>When Jakarta Authentication was configured with SimpleAuthConfigProvider
       as the default provider and multiple web application used that provider,
       the realm for the first web application to authenticate a request would
       be used for all web applications.</p>

    <p>This was fixed with commit
       <hashlink hash="043115414a39127cad015e9d285296e59c18bb41"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M4 to 9.0.121</p>

    <p><strong>Moderate: OpenSSL and OpenSSL-FFM TLS implementations ignore CRLs
       when certificate uses a keystore</strong>
       <cve>CVE-2026-73581</cve></p>

    <p>Both the OpenSSL and OpenSSL-FFM TLS implementations ignored CRLs when
       certificate used a keystore.</p>

    <p>This was fixed with commit
       <hashlink hash="2dce8f26b3ba6a89c8f172b94fa41a5fa2dcc361"/>.</p>

    <p>This issue was reported to the Tomcat security team on 11 August 2026.
       The issue was made public on 23 September 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.121</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.121" rtext="2026-08-18">

    <p><strong>Low: Authenticated WebSocket session survives end of HTTP
       session</strong>
       <cve>CVE-2026-73180</cve></p>

    <p>If the session ID for an authenticated HTTP session was changed after a
       WebSocket connection had been established under that authenticated HTTP
       session, the WebSokcet session would not be closed as required by the
       Jakarta WebSocket specification when the HTTP session ended.</p>

    <p>This was fixed with commit
       <hashlink hash="4b41a73a2f1a16647d7444ad6ee87d41a3ec414b"/>.</p>

    <p>This issue was reported to the Tomcat security team on 30 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0-M1 to 9.0.120</p>

    <p><strong>Important: DoS via allocation leak in HTTP/2 backlog tracking
       when a stream is reset</strong>
       <cve>CVE-2026-68763</cve></p>

    <p>An allocation leak in the HTTP/2 backlog tracking when a stream was reset
       could be manipulated to trigger a denial of service.</p>

    <p>This was fixed with commit
       <hashlink hash="0747dd58cc631f90e044df246bd2ede6e2b48250"/>.</p>

    <p>This issue was reported to the Tomcat security team on 16 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.39 to 9.0.120</p>

    <p><strong>Important: Principal lookup could fail open in some
       cases</strong>
       <cve>CVE-2026-68569</cve></p>

    <p>For some authentication methods (e.g. CLIENT-CERT, SPNEGO), a user would
       be authenticated even if the user did not exist in the
       DataSourceRealm and JDBCRealm.</p>

    <p>This was fixed with commit
       <hashlink hash="8efd51f061c026f6339bfa4fe4ef919a04ef130a"/>.</p>

    <p>This issue was reported to the Tomcat security team on 16 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.120</p>

    <p><strong>Low: Redirect after FORM authentication may bypass method
       specific constraints</strong>
       <cve>CVE-2026-68525</cve></p>

    <p>The FORM authentication process allowed the bypassing of a security
       constraint that limited user access to a resource POST but not GET.</p>

    <p>This was fixed with commit
       <hashlink hash="32f0c38526b4e655ff0c17cd97afedefc624fe43"/>.</p>

    <p>This issue was reported to the Tomcat security team on 15 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0-M1 to 9.0.120</p>

    <p><strong>Low: Servlet role references can bypass declarative role
       constraints</strong>
       <cve>CVE-2026-66422</cve></p>

    <p><code>security-role-ref</code> definitions were incorrectly used as role
       aliases within the Realm in additional to the correct usage with
       <code>Request.isUserInRole()</code>.</p>

    <p>This was fixed with commit
       <hashlink hash="bd05d5ced387da0c967bb232f7e3cd57685d2a7b"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.25 to 9.0.120</p>

    <p><strong>Low: DoS in WebSocket chat example</strong>
       <cve>CVE-2026-66299</cve></p>

    <p>The WebSocket chat example provided an unbounded buffer for undelivered
       messages. A maliciously slow client could cause the buffer to grow
       continuously, eventually leading to an memory exhaustion and failure of
       the Tomcat process.</p>

    <p>This was fixed with commit
       <hashlink hash="f6dda658e4eda2190de96219c182b9a75d27ab06"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 28 July 2026.</p>

    <p>Affects: 9.0.89 to 9.0.120<br/>
       Users who followed the security guidance to remove the examples web
       application are not affected.</p>

    <p><strong>Important: RewriteValve [N] restarts at the second rule and may
       bypass access control</strong>
       <cve>CVE-2026-65927</cve></p>

    <p>An off-by-one error impacting the [N] flag on the rewrite valves caused
       rewrite processing to restart at the second rule rather than the first
       rule.</p>

    <p>This was fixed with commits
       <hashlink hash="ffa86dc683645f784e36ec87236d51ea866dcadf"/> and
       <hashlink hash="b477537e68acfcaa7220f90b512bf8a72bf237dc"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0-M1 to 9.0.120</p>

    <p><strong>Low: Limited replay attack possible with DIGEST
       authentication</strong>
       <cve>CVE-2026-65905</cve></p>

    <p>If, before windowSize requests had been made, a client made a DIGEST
       authenticated request with a nonceCount on the upper boundary of the
       replay window then that request was replayable once only while the
       associated nonceCount remained within the replay window.</p>

    <p>This was fixed with commit
       <hashlink hash="a31181af45e494b6035575519f6d1d33875f050d"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.120</p>

    <p><strong>Moderate: HTTP/2 no-authority bypass of strict SNI
       validation</strong>
       <cve>CVE-2026-65637</cve></p>

    <p>The fix for <cve>CVE-2026-32990</cve> was incomplete.</p>

    <p>This was fixed with commit
       <hashlink hash="b823e88da077f5fa973e34d72359bded9f621e3c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.115 to 9.0.120</p>

    <p><strong>Low: TOCTOU when setting specific permissions for Unix Domain
       Sockets</strong>
       <cve>CVE-2026-65183</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 commits
       <hashlink hash="0206022f3aae65c5e0f23334b080849fdaaef444"/> and
       <hashlink hash="07e1b7d3da47a97d2861116f0ba5dd2b4018d256"/>.</p>

    <p>This issue was reported to the Tomcat security team on 3 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.42 to 9.0.120</p>

    <p><strong>Important: Security constraint bypass</strong>
       <cve>CVE-2026-65182</cve></p>

    <p>The security constraint processing enabled a security constraint bypass
       if a constraint for a longer path was specified before a more restrictive
       constraint for a shorter sub-path.</p>

    <p>This was fixed with commit
       <hashlink hash="b2c56ec8f20c66773a1a813034ffcdb60841f1cf"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 July 2026.
       The issue was made public on 25 August 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.120</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.120" rtext="2026-07-07">

    <p><strong>Low: EncryptInterceptor requirements not clearly
       documented</strong>
       <cve>CVE-2026-59084</cve></p>

    <p>The requirements to securely configure the EncryptInterceptor were not
       clearly documented.</p>

    <p>This was fixed with commit
       <hashlink hash="617d7275782bf58b45f6b7ea82c2edf16660e0b3"/>.</p>

    <p>This issue was reported to the Tomcat security team on 29 June 2026.
       The issue was made public on 14 July 2026.</p>

    <p>Affects: 9.0.13 to 9.0.119</p>

    <p><strong>Low: Incorrect URL decoding in RewriteValve may allow security
       control bypass</strong>
       <cve>CVE-2026-59083</cve></p>

    <p>Incorrect decoding of <code>+</code> in rewritten URIs to a single space
       could allow security control bypass for some configurations.</p>

    <p>This was fixed with commit
       <hashlink hash="a520aecb325e2279f2bf3a7a090ca7f61ed1c7af"/>.</p>

    <p>This issue was identified by the Tomcat security team on 26 June 2026.
       The issue was made public on 14 July 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.119</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.119" rtext="2026-06-23">

    <p><strong>Moderate: Security constraints for default servlet ignored
       method</strong>
       <cve>CVE-2026-55956</cve></p>

    <p>If security constraints were specified for the default servlet, any
       method or method omission configured as part of the constraint was
       ignored.</p>

    <p>This was fixed with commit
       <hashlink hash="a0374c450970760efafbd8806a1db278830ba7bd"/>.</p>

    <p>This issue was reported to the Tomcat security team on 15 June 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.118</p>

    <p><strong>Low: EncryptInterceptor not protected against replay
       attacks</strong>
       <cve>CVE-2026-55955</cve></p>

    <p>Contrary to the documentation, the EncryptInterceptor was not protected
       against replay attacks.</p>

    <p>This was fixed with commit
       <hashlink hash="6a7a432cd7fb4ef358dc12e8da99cf3ab320f3fe"/>.</p>

    <p>This issue was reported to the Tomcat security team on 17 June 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.13 to 9.0.118</p>

    <p><strong>Low: Logged effective web.xml is incomplete</strong>
       <cve>CVE-2026-55276</cve></p>

    <p>Logic errors in the effective web.xml generation meant that neither
    special roles nor empty authorization constraints were included in the
    logged effective web.xml.</p>

    <p>This was fixed with commit
       <hashlink hash="3ca8cae5fd3796b1bd9759e11b0e238161e7a39c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 16 June 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.118</p>

    <p><strong>Low: Invalid CRL configuration doesn't trigger failure for FFM
       Connector</strong>
       <cve>CVE-2026-53434</cve></p>

    <p>If an FFM connector was configured with invalid CRLs, the invalid CRLs
       were ignored meaning invalid certificates could be accepted.</p>

    <p>This was fixed with commit
       <hashlink hash="c48ac39c27f4494f8c96b9d56a487253e362d276"/>.</p>

    <p>This issue was reported to the Tomcat security team on 8 June 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.83 to 9.0.118</p>

    <p><strong>Low: Bad ornext processing in RewriteValve</strong>
       <cve>CVE-2026-53404</cve></p>

    <p>If a request matched the first condition in an OR chain, subsequent
    non-OR conditions were skipped and the rewrite succeeded.</p>

    <p>This was fixed with commit
       <hashlink hash="fe06ae8a71997061596f54189dae1b1b5da75430"/>.</p>

    <p>This issue was reported to the Tomcat security team on 28 May 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.118</p>

    <p><strong>Low: XSS in number guess example</strong>
       <cve>CVE-2026-50229</cve></p>

    <p>The use of wild card property mapping resulted in some properties, that
       were intended to be internal only, being exposed to clients allowing an
       XSS attack.</p>

    <p>This was fixed with commit
       <hashlink hash="de5a950415fc67713f17fab63d0c7809e0fca80b"/>.</p>

    <p>This issue was reported to the Tomcat security team on 11 May 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.118</p>

  </section>
  <section name="Fixed in Apache Tomcat 9.0.118" rtext="2026-05-10">

    <p><strong>Moderate: Security constraints not correctly applied</strong>
       <cve>CVE-2026-43515</cve></p>

    <p>When multiple security constraints defined an HTTP method constraint for
       the same extension pattern, only the first method constraint was
       applied.</p>

    <p>This was fixed with commit
       <hashlink hash="db919ff9912b4d61d1b702a1342b8bde39270031"/>.</p>

    <p>This issue was reported to the Tomcat security team on 20 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

    <p><strong>Low: AJP secret compared in non-constant time</strong>
       <cve>CVE-2026-43514</cve></p>

    <p>The AJP secret was compared in non-constant time allowing an attacker on
       the local network to mount a timing attack to determine the AJP
       secret.</p>

    <p>This was fixed with commits
       <hashlink hash="933dcdbf2515972280002929e7e597dead2e9ffa"/> and
       <hashlink hash="2e676264ce27448a4d4841e42c1238bd10ca3755"/>.</p>

    <p>This issue was reported to the Tomcat security team on 20 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

    <p><strong>Low: LockOutRealm treats user names as case-sensitive</strong>
       <cve>CVE-2026-43513</cve></p>

    <p>The LockOut Realm treated user names as case sensitive meaning that, for
       Realms where the user name was case insensitive, the LockOut Realm was
       not as effective at blocking brute force attacks against a user's
       password.</p>

    <p>This was fixed with commit
       <hashlink hash="6dd75beb55bd42fc5f78e929596b25018cd17717"/>.</p>

    <p>This issue was reported to the Tomcat security team on 20 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

    <p><strong>Moderate: Digest authenticator will authenticate any unknown user</strong>
       <cve>CVE-2026-43512</cve></p>

    <p>When DIGEST authentication was configured, any user not known to the
       configured Realm would be authenticated if they presented the password
       "null".</p>

    <p>This was fixed with commit
       <hashlink hash="6565a6cb6499e56fe2f34457cec99f9d1c4f39e9"/>.</p>

    <p>This issue was reported to the Tomcat security team on 20 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

    <p><strong>Low: WebSocket authentication header exposure</strong>
       <cve>CVE-2026-42498</cve></p>

    <p>If a WebSocket request was redirected after authentication, Tomcat's
       WebSocket client would present the most recent authentication header to
       the redirect target host.</p>

    <p>This was fixed with commit
       <hashlink hash="169d725788ea6aec217ecac70fe4161c837ba423"/>.</p>

    <p>This issue was reported to the Tomcat security team on 21 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.2 to 9.0.117</p>

    <p><strong>Low: HTTP/2 request headers not validated</strong>
       <cve>CVE-2026-41293</cve></p>

    <p>HTTP/2 request headers were not validated which may have triggered
       unexpected application behaviour if the application (quite reasonably)
       assumed that header value exposed through the Servlet API would be
       specification compliant.</p>

    <p>This was fixed with commits
       <hashlink hash="cf9452443bcbf3b1a4b435ef7d624364f1b65ca3"/>,
       <hashlink hash="1c70480466572c9192ed412ebefcd43fc63137fd"/> and
       <hashlink hash="57c2b3bfd62792631e1df24cf4237b990a0b36fa"/>.</p>

    <p>This issue was reported to the Tomcat security team on 15 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

    <p><strong>Low: Unbounded read in WebDAV LOCK and PROPFIND handling</strong>
       <cve>CVE-2026-41284</cve></p>

    <p>No limit was enforced on the request body for WebDAV LOCK or PROPFIND
       requests which were available to unauthenticated users.</p>

    <p>This was fixed with commit
       <hashlink hash="17dacd9aa48628da2eba37a9ab743c0b6c71685c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 11 April 2026.
       The issue was made public on 12 May 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.117</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.117" rtext="2026-04-03">

    <p><strong>Moderate: OCSP checks sometimes soft-fail with FFM even when
       soft-fail is disabled</strong>
       <cve>CVE-2026-34500</cve></p>

    <p>CLIENT_CERT authentication does not fail as expected for some scenarios
       when soft fail is disabled and FFM is used.</p>

    <p>This was fixed with commit
       <hashlink hash="ff589ab26e8250a2ca4286d986305318c033ff9f"/>.</p>

    <p>This issue was reported to the Tomcat security team on 25 March 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.92 to 9.0.116</p>

    <p><strong>Low: Cloud membership for clustering component exposed the
       Kubernetes bearer token</strong>
       <cve>CVE-2026-34487</cve></p>

    <p>The cloud membership for clustering component exposed the Kubernetes
       bearer token in log messages.</p>

    <p>This was fixed with commit
       <hashlink hash="f593292a082e5ef9336a8db2b4b522f7f3e36976"/>.</p>

    <p>This issue was reported to the Tomcat security team on 25 March 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.13 to 9.0.116</p>

    <p><strong>Important: The fix for <cve>CVE-2026-29146</cve> allowed the
       bypass of the EncryptInterceptor</strong>
       <cve>CVE-2026-34486</cve></p>

    <p>An error in the fix for <cve>CVE-2026-29146</cve> allowed the
       EncryptInterceptor to be bypassed.</p>

    <p>This was fixed with commit
       <hashlink hash="776e12b3e2b0b4507b8a3b62c187ceb0b74bf418"/>.</p>

    <p>This issue was reported to the Tomcat security team on 26 March 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.116</p>

    <p><strong>Low: Incomplete escaping of JSON access logs</strong>
       <cve>CVE-2026-34483</cve></p>

    <p>Incomplete escaping when non-default values were used for the Connector
       attributes relaxedPathChars and/or relaxedQueryChars allowed the
       injection of arbitrary JSON into the JSON access log.</p>

    <p>This was fixed with commit
       <hashlink hash="97566842589d0b80de138ca719378861fd017d68"/>.</p>

    <p>This issue was reported to the Tomcat security team on 25 March 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.40 to 9.0.116</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.116" rtext="2026-03-20">
  
    <p><strong>Moderate: The fix for <cve>CVE-2025-66614</cve> was
       incomplete</strong>
       <cve>CVE-2026-32990</cve></p>

    <p>The validation of SNI name and host name did not take account of possible
       differences in case allowing the strict SNI checks to be bypassed.</p>

    <p>This was fixed with commit
       <hashlink hash="95f7778248cac46d03e6af04de9c72a598be3a53"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 March 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.113 to 9.0.115</p>

    <p><strong>Important: EncryptInterceptor vulnerable to padding oracle attack
       by default</strong>
       <cve>CVE-2026-29146</cve></p>

    <p>The EncryptInterceptor used CBC by default which is vulnerable to a
       padding Oracle attack.</p>

    <p>This was fixed with commit
       <hashlink hash="0112ed22abfccc3d54e44d91eb08804d0886acd1"/>.</p>

    <p>This issue was reported to the Tomcat security team on 22 February 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.13 to 9.0.115</p>

    <p><strong>Moderate: OCSP checks sometimes soft-fail even when soft-fail is
       disabled</strong>
       <cve>CVE-2026-29145</cve></p>

    <p>CLIENT_CERT authentication did not fail OCSP checks as expected for some
       scenarios when soft fail was disabled.</p>

    <p>This was fixed with commit
       <hashlink hash="d1406df5ae0326f39f54c3f64ac30d8fca55cd5b"/>.</p>

    <p>This issue was reported to the Tomcat security team on 26 February 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.83 to 9.0.115</p>

    <p><strong>Low: Configured TLS cipher preference order not preserved</strong>
       <cve>CVE-2026-29129</cve></p>

    <p>The additional of the ability to configure TLS 1.3 cipher suites did not
       preserve the order of the configured cipher suites and ciphers.</p>

    <p>This was fixed with commit
       <hashlink hash="6db238562ec36ab1106db4d04843f8b33e7a0c06"/>.</p>

    <p>This was reported as a bug on 20 February 026 and the security
       implications identified by the Tomcat security team the same day.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.114 to 9.0.115</p>

    <p><strong>Low: Occasionally open redirect</strong>
       <cve>CVE-2026-25854</cve></p>

    <p>When a Tomcat node in a cluster with the LoadBalancerDrainingValve was in
       the disabled (draining) state, a specially crafted URL could be used to
       trigger a redirect to a URI of the attackers choice.</p>

    <p>This was fixed with commit
       <hashlink hash="c5a45ae68d07f7a07be2a875e5b6772d66c4e5d0"/>.</p>

    <p>This issue was reported to the Tomcat security team on 30 January 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.0.M23 to 9.0.115</p>

    <p><strong>Low: Request smuggling via invalid chunk extension</strong>
       <cve>CVE-2026-24880</cve></p>

    <p>Tomcat did not validate that contents of HTTP/1.1 chunk extensions. This
       enabled a request smuggling attack if a reverse proxy in front of Tomcat
       allowed CRLF sequences in an otherwise valid chunk extension.</p>

    <p>This was fixed with commits
       <hashlink hash="1b586d6aa8ae65726da5fa8799427b5d4718478a"/> and
       <hashlink hash="6d478dbe18b7c4bb671c30fedf130309b0dab77c"/>.</p>

    <p>This issue was reported to the Tomcat security team on 19 January 2026.
       The issue was made public on 9 April 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.115</p>

  </section>
  <section name="Fixed in Apache Tomcat 9.0.115" rtext="2026-01-23">

    <p><strong>Moderate: Incomplete OCSP verification checks</strong>
       <cve>CVE-2026-24734</cve></p>

    <p>When using an OCSP responder, Tomcat's FFM integration with OpenSSL did
       not complete verification or freshness checks on the OCSP response which
       could allow certificate revocation to be bypassed.</p>

    <p>Affects: 9.0.83 to 9.0.114</p>

    <p>This issue was reported to the Tomcat security team on 2 November 2025.
       The issue was made public on 17 February 2026.</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.113" rtext="2025-12-07">

    <p><strong>Low: Security constraint bypass</strong>
       <cve>CVE-2026-24733</cve></p>

    <p>Tomcat did not limit HTTP/0.9 requests to the GET method. If a security
       constraint was configured to allow HEAD requests to a URI but deny GET
       requests, the user could bypass that constraint on GET requests by
       sending a (specification invalid) HEAD request using HTTP/0.9.</p>

    <p>This was fixed with commit
       <hashlink hash="2e2fa23f2635bbb819759576a2f2f5e64ecf7c5f"/>.</p>

    <p>This issue was identified by the Tomcat security team on 26 November
       2025. The issue was made public on 17 February 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.112</p>

    <p><strong>Moderate: Client certificate verification bypass due to virtual
       host mapping</strong>
       <cve>CVE-2025-66614</cve></p>

    <p>Tomcat did not validate that the host name provided via the SNI extension
       was the same as the host name provided in the HTTP host header field. If
       Tomcat was configured with more than one virtual host and the TLS
       configuration for one of those hosts did not require client certificate
       authentication but another one did, it was possible for a client to
       bypass the client certificate authentication by sending different host
       names in the SNI extension and the HTTP host header field.</p>

    <p>The vulnerability only applies if client certificate authentication is
       only enforced at the Connector. It does not apply if client certificate
       authentication is enforced at the web application.</p>

    <p>This was fixed with commits
       <hashlink hash="152c14885d45f5e0a8b59bd9f93c289cfe20ce30"/>,
       <hashlink hash="a4aa74232e826028cd2f7ba0445caf8a8b52c509"/> and
       <hashlink hash="9276b5e783c8cd5b3fe2bb716306b65004bdd940"/>.</p>

    <p>This issue was reported to the Tomcat security team on 15 October 2025.
       The issue was made public on 17 February 2026.</p>

    <p>Affects: 9.0.0.M1 to 9.0.112</p>

  </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>This issue was reported to the Tomcat security team on 7 September 2025.
       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.0.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>This issue was reported to the Tomcat security team on 5 August 2025. 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>This issue was reported to the Tomcat security team on 11 August 2025.
       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
       reset</strong>
       <cve>CVE-2025-48989</cve></p>

    <p>Tomcat's HTTP/2 implementation was vulnerable to the made you reset
       attack. The denial of service typically manifested as an
       <code>OutOfMemoryError</code>.</p>
       
    <p>This was fixed with commit
       <hashlink hash="f36b8a4eea4ce8a0bc035079e1d259d29f5eb7bf"/>.</p>

    <p>This issue was reported to the ASF security team on 29 May 2025. The
       issue was made public on 13 August 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.107</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.107" rtext="2025-07-04">

    <p><strong>Important: APR/Native Connector crash leading to DoS</strong>
       <cve>CVE-2025-52434</cve></p>

    <p>A race condition on connection close could trigger a JVM crash when using
       the APR/Native connector leading to a DoS. This was particularly
       noticeable with client initiated closes of HTTP/2 connections.</p>

    <p>This was fixed with commit
       <hashlink hash="8a83c3c42d20762782678932c14005cd3397a018"/>.</p>

    <p>This issue was reported to the Tomcat security team on 6 June 2025. The
       issue was made public on 10 July 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.106</p>

    <p><strong>Low: DoS due to overflow in file upload limit</strong>
       <cve>CVE-2025-52520</cve></p>

    <p>For some unlikely configurations of multipart upload, an Integer Overflow
       vulnerability could lead to a DoS via bypassing of size limits.</p>

    <p>This was fixed with commit
       <hashlink hash="927d66fbc294cb65242102b817a45fd80834e040"/>.</p>

    <p>This issue was reported to the Tomcat security team on 7 June 2025. The
       issue was made public on 10 July 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.106</p>

    <p><strong>Important: DoS via excessive HTTP/2 streams</strong>
       <cve>CVE-2025-53506</cve></p>

    <p>An uncontrolled resource consumption vulnerability if an HTTP/2 client
       did not acknowledge the initial settings frame that reduces the maximum
       permitted concurrent streams could result in a DoS.</p>

    <p>This was fixed with commit
       <hashlink hash="434772930f362145516dd60681134e7f0cf8115b"/>.</p>

    <p>This issue was reported to the Tomcat security team on 28 June 2025. The
       issue was made public on 10 July 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.106</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.106" rtext="2025-06-10">
  
    <p><strong>Moderate: Session fixation possible via rewrite valve</strong>
       <cve>CVE-2025-55668</cve></p>

    <p>If the rewrite valve was enabled for a web application, an attacker was
       able to craft a URL that, if a victim clicked on it, would cause the
       victim's interaction with that resource to occur in the context of the
       attacker's session.</p>

    <p>This was fixed with commit
       <hashlink hash="9c3673ba04009377cb0c81ccb6cf5078aec1aa95"/>.</p>

    <p>This issue was reported to the Tomcat security team on 30 May 2025. The
       issue was made public on 13 August 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.105</p>

    <p><strong>Moderate: Security constraint bypass for PreResources and
       PostResources</strong>
       <cve>CVE-2025-49125</cve></p>

    <p>When using PreResources or PostResources mounted other than at the root
       of the web application, it was possible to access those resources via an
       unexpected path. That path was likely not to be protected by the same
       security constraints as the expected path, allowing those security
       constraints to be bypassed.</p>

    <p>This was fixed with commit
       <hashlink hash="9418e3ff9f1f4c006b4661311ae9376c52d162b9"/>.</p>

    <p>This issue was reported to the Tomcat security team on 30 May 2025. The
       issue was made public on 16 June 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.105</p>

    <p><strong>Low: Side-loading via Tomcat installer for Windows</strong>
       <cve>CVE-2025-49124</cve></p>

    <p>During installation, the Tomcat installer for Windows used icacls.exe
       without specifying a full path. This enabled a side-loading
       vulnerability.</p>

    <p>This was fixed with commit
       <hashlink hash="28726cc2e63bed68771f5eb0f65a78dc7080571823"/>.</p>

    <p>This issue was reported to the Tomcat security team on 30 May 2025. The
       issue was made public on 16 June 2025.</p>

    <p>Affects: 9.0.23 to 9.0.105</p>

    <p><strong>Important: DoS in multipart upload</strong>
       <cve>CVE-2025-48988</cve></p>

    <p>Tomcat used the same limit for both request parameters and parts in a
       multipart request. Since uploaded parts also include headers which must
       be retained, processing multipart requests can result in significantly
       more memory usage. A specially crafted request that used a large number
       of parts could trigger excessive memory usage leading to a DoS. The
       maximum number of parts is now configurable (maxPartCount on the
       Connector) with a default of 10 parts.</p>

    <p>This was fixed with commit
       <hashlink hash="ee8042ffce4cb9324dfd79efda5984f37bbb6910"/>.</p>

    <p>This issue was reported to the ASF security team on 16 May 2025. The
       issue was made public on 16 June 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.105</p>

    <p><strong>Important: DoS in Commons FileUpload</strong>
       <cve>CVE-2025-48976</cve></p>

    <p>Apache Commons FileUpload provided a hard-coded limit of 10kB for the
       size of the headers associated with a multipart request. A specially
       crafted request that used a large number of parts with large headers
       could trigger excessive memory usage leading to a DoS. This limit is
       now configurable (maxPartHeaderSize on the Connector) with a default of
       512 bytes.</p>

    <p>This was fixed with commit
       <hashlink hash="97790a35a27d236fa053e660676c3f8196284d93"/>.</p>

    <p>This issue was reported to the ASF security team on 16 May 2025. The
       issue was made public on 16 June 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.105</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.105" rtext="2025-05-12">

    <p><strong>Low: CGI security constraint bypass</strong>
       <cve>CVE-2025-46701</cve></p>

    <p>When running on a case insensitive file system with security constraints
       configured for the <code>pathInfo</code> component of a URL that mapped
       to the CGI servlet, it was possible to bypass those security constraints
       with a specially crafted URL.</p>

    <p>This was fixed with commits
       <hashlink hash="8df00018a252baa9497615d6420fb6c10466fa74"/> and
       <hashlink hash="8cb95ff03221067c511b3fa66d4f745bc4b0a605"/>.</p>

    <p>This issue was reported to the Tomcat security team on 7 April 2025. The
       issue was made public on 29 May 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.104</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.104" rtext="2025-04-08">

    <p><i>Note: The issues below were fixed in Apache Tomcat 9.0.103 but the
       release vote for the 9.0.103 release candidate did not pass. Therefore,
       although users must download 9.0.104 to obtain a version that includes a
       fix for these issues, version 9.0.103 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Low: Rewrite rule bypass</strong> <cve>CVE-2025-31651</cve></p>

    <p>For a subset of unlikely rewrite rule configurations, it was possible for
       a specially crafted request to bypass some rewrite rules. If those
       rewrite rules effectively enforced security constraints, those
       constraints could be bypassed.</p>

    <p>This was fixed with commits
       <hashlink hash="ee3ab548e92345eca0cbd1f01649eb36c6f29454"/> and
       <hashlink hash="175dc75fc428930034a6c93fb52f830d955d8e64"/>.</p>

    <p>This issue was reported to the Tomcat security team on 28 February 2025.
       The issue was made public on 28 April 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.102</p>

    <p><strong>Important: Denial of Service via invalid HTTP priority
       header</strong> <cve>CVE-2025-31650</cve></p>

    <p>Incorrect error handling for some invalid HTTP priority headers resulted
       in incomplete clean-up of the failed request which created a memory leak.
       A large number of such requests could trigger an
       OutOfMemoryException resulting in a denial of service.</p>

    <p>This was fixed with commits
       <hashlink hash="40ae788c2e64d018b4e58cd4210bb96434d0100d"/>,
       <hashlink hash="b98e74f517b36929f4208506e5adad22cb767baa"/> and
       <hashlink hash="b7674782679e1514a0d154166b1d04d38aaac4a9"/>.</p>

    <p>This issue was not disclosed responsibly. It was reported via the public
       bug tracker on 13 March 2025. The CVE was published on 28 April 2025.</p>

    <p>Affects: 9.0.76 to 9.0.102</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.102" rtext="2025-03-06">

    <p><strong>Important: Authentication bypass with JNDIRealm and GSSAPI
       authenticated bind</strong>
       <cve>CVE-2026-55957</cve></p>

    <p>When the JNDIRealm was configured to authenticate binds using GSSAPI, an
       attacker was able authenticate without providing the correct
       password.</p>

    <p>This was fixed with commits
       <hashlink hash="c32bbd37ea9ee0aaab848af4ee1c9a76e84240ea"/>.</p>

    <p>This issue was reported to the Tomcat security team on 14 June 2026.
       The issue was made public on 29 June 2026.</p>

    <p>Affects: 9.0.0-M1 to 9.0.100</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.99" rtext="2025-02-10">
  
    <p><strong>Important: Remote Code Execution and/or Information disclosure
       and/or malicious content added to uploaded files via write enabled
       Default Servlet - </strong> <cve>CVE-2025-24813</cve></p>

    <p>The original implementation of partial PUT used a temporary file based on
       the user provided file name and path with the path separator replaced by
       ".".</p>

    <p>If all of the following were true, a malicious user was able to view
       security sensitive files and/or inject content into those files:</p>

    <ul>
      <li>writes enabled for the default servlet (disabled by default)</li>
      <li>support for partial PUT (enabled by default)</li>
      <li>a target URL for security sensitive uploads that is a sub-directory of
          a target URL for public uploads</li>
      <li>attacker knowledge of the names of security sensitive files being
          uploaded</li>
      <li>the security sensitive files also being uploaded via partial PUT</li>
    </ul>

    <p>If all of the following were true, a malicious user was able to perform
       remote code execution:</p>

    <ul>
      <li>writes enabled for the default servlet (disabled by default)</li>
      <li>support for partial PUT (enabled by default)</li>
      <li>application was using Tomcat's file based session persistence with the
          default storage location</li>
      <li>application included a library that may be leveraged in a
          deserialization attack</li>
    </ul>

    <p>This was fixed with commit
       <hashlink hash="eb61aade8f8daccaecabf07d428b877975622f72"/>.</p>

    <p>This issue was reported to the Tomcat security team on 13 January 2025.
       The issue was made public on 10 March 2025.</p>

    <p>Affects: 9.0.0.M1 to 9.0.98</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.98" rtext="2024-12-09">
  
    <p><strong>Important: Remote Code Execution via write enabled Default
       Servlet. Mitigation for CVE-2024-50379 was incomplete - </strong>
       <cve>CVE-2024-56337</cve></p>

    <p>The previous mitigation for <cve>CVE-2024-50379</cve> was incomplete. In
       addition to upgrading to 9.0.98 or later, users running Tomcat on a case
       insensitive file system with the default servlet write enabled may need
       additional configuration depending on the version of Java being used:
       <ul>
       <li>running on Java 8 or Java 11: the system property
           <code>sun.io.useCanonCaches</code> must be explicitly set to
           <code>false</code> (it defaults to <code>true</code>)</li>
       <li>running on Java 17: the system property
           <code>sun.io.useCanonCaches</code>, if set, must be set to
           <code>false</code> (it defaults to <code>false</code>)</li>
       <li>running on Java 21 onwards: no further configuration is required (the
           system property and the problematic cache have been removed)</li>
       </ul></p>

    <p>This issue was reported to the Tomcat security team on 17 December 2024.
       The issue was made public on 20 December 2024.</p>

    <p>Affects: 9.0.0.M1 to 9.0.97</p>
    
    <p><strong>Low: DoS in examples web application</strong>
       <cve>CVE-2024-54677</cve></p>

    <p>Numerous examples in the examples web application did not place limits on
       uploaded data enabling an OutOfMemoryError to be triggered causing a
       denial of service.</p>

    <p>This was fixed with commits
       <hashlink hash="1d88dd3ffaed76188dd4ee32ce77709ce6e153cd"/>,
       <hashlink hash="721544ea28e92549824b106be954a9f411867a1c"/>,
       <hashlink hash="84065e26ca4555e63a922bb29b13b0a1c86b7654"/>,
       <hashlink hash="3315a9027a7eaab18f42625b97b569940ff1365d"/>,
       <hashlink hash="c2f7ce21c3fb12caefee87c517a8bb4f80700044"/>,
       <hashlink hash="75ff7e8622edcc024b268677aa789ee8f0880ecc"/>,
       <hashlink hash="4d5cc6538d91386f950373ac8120e98c2c78ed3a"/>,
       <hashlink hash="84c4af76e7a10fc7f8630ce62e6a46632ea4a90e"/> and
       <hashlink hash="9ffd23fc27f5d1fc95bf97e5cea175c8968f4533"/>.</p>

    <p>This issue was reported to the Tomcat security team on 23 November 2024.
       The issue was made public on 17 December 2024.</p>

    <p>Affects: 9.0.0.M1 to 9.0.97</p>

    <p><strong>Important: Remote Code Execution via write enabled Default Servlet</strong>
       <cve>CVE-2024-50379</cve></p>

    <p>If the default servlet is write enabled (<code>readonly</code>
       initialisation parameter set to the non-default value of
       <code>false</code>) for a case insensitive file system, concurrent read
       and upload under load of the same file can bypass Tomcat's case
       sensitivity checks and cause an uploaded file to be treated as a JSP
       leading to remote code execution.</p>

    <p>This was fixed with commits
       <hashlink hash="43b507ebac9d268b1ea3d908e296cc6e46795c00"/> and
       <hashlink hash="631500b0c9b2a2a2abb707e3de2e10a5936e5d41"/>.</p>

    <p>This issue was reported to the Tomcat security team on 18 October 2024.
       The issue was made public on 17 December 2024.</p>

    <p>Affects: 9.0.0.M1 to 9.0.97</p>
  
  </section>

  <section name="Fixed in Apache Tomcat 9.0.97" rtext="2024-11-09">

    <p><strong>Important: XSS in generated JSPs</strong>
       <cve>CVE-2024-52318</cve></p>

    <p>The fix for improvement <bug>69333</bug> caused pooled JSP tags not to be
       released after use which in turn could cause output of some tags not to
       escaped as expected. This unescaped output could lead to XSS.</p>

    <p>This was fixed with commit
       <hashlink hash="9813c5dd3259183f659bbb83312a5cf673cc1ebf"/>.</p>

    <p>This issue was not disclosed responsibly. It was reported via the public
       bug tracker on 6 November 2024. The CVE was published on 18 November
       2024.</p>

    <p>Affects: 9.0.96</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.96" rtext="2024-10-09">

    <p><strong>Important: Request and/or response mix-up</strong>
       <cve>CVE-2024-52317</cve></p>

    <p>Incorrect recycling of the request and response used by HTTP/2 requests
       could lead to request and/or response mix-up between users.</p>

    <p>This was fixed with commit
       <hashlink hash="47307ee27abcdea2ee40e33897aca760083de46a"/>.</p>

    <p>This issue was identified by the Tomcat Security Team on 1 October 2024.
       The issue was made public on 18 November 2024.</p>

    <p>Affects: 9.0.92 to 9.0.95</p>

    <p><strong>Low: Authentication Bypass</strong>
       <cve>CVE-2024-52316</cve></p>

    <p>If Tomcat was configured to use a custom Jakarta Authentication (formerly
       JASPIC) ServerAuthContext component which may throw an exception during
       the authentication process without explicitly setting an HTTP status to
       indicate failure, the authentication may not have failed, allowing the
       user to bypass the authentication process. There are no known Jakarta
       Authentication components that behave in this way.</p>

    <p>This was fixed with commit
       <hashlink hash="7532f9dc4a8c37ec958f79dc82c4924a6c539223"/>.</p>

    <p>This issue was identified by the Tomcat Security Team on 19 September
       2024. The issue was made public on 18 November 2024.</p>

    <p>Affects: 9.0.0-M1 to 9.0.95</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.90" rtext="2024-06-19">

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2024-34750</cve></p>

    <p>When processing an HTTP/2 stream, Tomcat did not handle some cases of
       excessive HTTP headers correctly. This led to a miscounting of active
       HTTP/2 streams which in turn led to the use of an incorrect infinite
       timeout which allowed connections to remain open which should have been
       closed.</p>

    <p>This was fixed with commit
       <hashlink hash="9fec9a82887853402833a80b584e3762c7423f5f"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 4 May 2024. The
       issue was made public on 3 July 2024.</p>

    <p>Affects: 9.0.0-M1 to 9.0.89</p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2024-38286</cve></p>

    <p>Tomcat, under certain configurations on any platform, allows an attacker
       to cause an OutOfMemoryError by abusing the TLS handshake process.</p>

    <p>This was fixed with commit
       <hashlink hash="76c5cce6f0bcef14b0c21c38910371ca7d322d13"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 4 June 2024. The
       issue was made public on 23 September 2024.</p>

    <p>Affects: 9.0.13 to 9.0.89</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.86" rtext="2024-02-19">
  
    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2024-23672</cve></p>

    <p>It was possible for a WebSocket client to keep a WebSocket connection
       open leading to increased resource consumption.</p>

    <p>This was fixed with commit
       <hashlink hash="52d6650e062d880704898d7d8c1b2b7a3efe8068"/>.</p>

    <p>This issue was identified by the Tomcat Security Team on 17 January 2024.
       The issue was made public on 13 March 2024.</p>

    <p>Affects: 9.0.0-M1 to 9.0.85</p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2024-24549</cve></p>

    <p>When processing an HTTP/2 request, if the request exceeded any of the
       configured limits for headers, the associated HTTP/2 stream was not reset
       until after all of the headers had been processed.</p>
       
    <p>This was fixed with commit
       <hashlink hash="8e03be9f2698f2da9027d40b9e9c0c9429b74dc0"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 24 January 2024. The
       issue was made public on 13 March 2024.</p>

    <p>Affects: 9.0.0-M1 to 9.0.85</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.83" rtext="2023-11-15">

    <p><strong>Important: Request smuggling</strong>
       <cve>CVE-2023-46589</cve></p>

    <p>Tomcat did not correctly parse HTTP trailer headers. A specially crafted
       trailer header that exceeded the header size limit could cause Tomcat to
       treat a single request as multiple requests leading to the possibility of
       request smuggling when behind a reverse proxy.</p>

    <p>This was fixed with commit
       <hashlink hash="7a2d8818fcea0b51747a67af9510ce7977245ebd"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 20 October 2023.
       The issue was made public on 28 November 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.82</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.81" rtext="2023-10-10">

    <p><strong>Important: Request smuggling</strong>
       <cve>CVE-2023-45648</cve></p>

    <p>Tomcat did not correctly parse HTTP trailer headers. A specially crafted,
       invalid trailer header could cause Tomcat to treat a single request as
       multiple requests leading to the possibility of request smuggling when
       behind a reverse proxy.</p>

    <p>This was fixed with commit
       <hashlink hash="59583245639d8c42ae0009f4a4a70464d3ea70a0"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 12 September 2023.
       The issue was made public on 10 October 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.80</p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2023-44487</cve></p>

    <p>Tomcat's HTTP/2 implementation was vulnerable to the rapid reset
       attack. The denial of service typically manifested as an
       <code>OutOfMemoryError</code>.</p>

    <p>This was fixed with commit
       <hashlink hash="6d1a9fd6642387969e4410b9989c85856b74917a"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 14 September 2023.
       The issue was made public on 10 October 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.80</p>

    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2023-42795</cve></p>

    <p>When recycling various internal objects, including the request and the
       response, prior to re-use by the next request/response, an error could
       cause Tomcat to skip some parts of the recycling process leading to
       information leaking from the current request/response to the next.</p>

    <p>This was fixed with commit
       <hashlink hash="44d05d75d696ca10ce251e4e370511e38f20ae75"/>.</p>

    <p>This issue was identified by the Tomcat Security Team on 13 September
       2023. The issue was made public on 10 October 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.80</p>

    <p><strong>Low: Denial of Service</strong>
       <cve>CVE-2023-42794</cve></p>

    <p>Tomcat's internal fork of a Commons FileUpload included an unreleased, in
       progress refactoring that exposed a potential denial of service on
       Windows if a web application opened a stream for an uploaded file but
       failed to close the stream. The file would never be deleted from disk
       creating the possibility of an eventual denial of service due to the disk
       being full.</p>

    <p>This was fixed with commit
       <hashlink hash="43b882b8a577684498ab9b8851aa0427216784f7"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 1 September
       2023. The issue was made public on 10 October 2023.</p>

    <p>Affects: 9.0.70 to 9.0.80</p>

  </section>
 
  <section name="Fixed in Apache Tomcat 9.0.80" rtext="2023-08-25">

    <p><strong>Moderate: Open redirect</strong>
       <cve>CVE-2023-41080</cve></p>

    <p>If the ROOT (default) web application is configured to use FORM
       authentication then it is possible that a specially crafted URL could be
       used to trigger a redirect to an URL of the attackers choice.</p>
       
    <p>This was fixed with commit
       <hashlink hash="77c0ce2d169efa248b64b992e547aad549ec906b"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 17 August 2023. The
       issue was made public on 22 August 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.79</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.75" rtext="2023-05-10">

    <p><strong>Important: Information disclosure</strong>
       <cve>CVE-2023-34981</cve></p>

    <p>The fix for bug <bug>66512</bug> introduced a regression that was fixed
       as bug <bug>66591</bug>. The regression meant that, if a response did not
       have any HTTP headers set, no AJP <code>SEND_HEADERS</code> message would
       be sent which in turn meant that at least one AJP based proxy
       (mod_proxy_ajp) would use the response headers from the previous request
       for the current request leading to an information leak.</p>
       
    <p>This was fixed with commit
       <hashlink hash="2f0ca2378415f4cf0748f4bc8fa955f41f803fa5"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 24 May 2023. The
       issue was made public on 21 June 2023.</p>

    <p>Affects: 9.0.74</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.74" rtext="2023-04-18">

    <p><strong>Moderate: Apache Tomcat denial of service</strong>
       <cve>CVE-2023-28709</cve></p>

    <p>The fix for <cve>CVE-2023-24998</cve> was incomplete. If non-default HTTP
       connector settings were used such that the <code>maxParameterCount</code>
       could be reached using query string parameters and a request was
       submitted that supplied exactly <code>maxParameterCount</code> parameters
       in the query string, the limit for uploaded request parts could be
       bypassed with the potential for a denial of service to occur.</p>
       
    <p>This was fixed with commit
       <hashlink hash="fbd81421629afe8b8a3922d59020cde81caea861"/>.</p>

    <p>This issue was reported to the Tomcat Security Team on 13 March 2023. The
       issue was made public on 22 May 2023.</p>

    <p>Affects: 9.0.71 to 9.0.73</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.72" rtext="2023-02-23">

    <p><strong>Important: Apache Tomcat information disclosure</strong>
       <cve>CVE-2023-28708</cve></p>

    <p>When using the <code>RemoteIpFilter</code> with requests received from a
    reverse proxy via HTTP that include the <code>X-Forwarded-Proto</code>
    header set to <code>https</code>, session cookies created by Tomcat did not
    include the secure attribute. This could result in the user agent
    transmitting the session cookie over an insecure channel.</p>
       
    <p>This was fixed with commit
       <hashlink hash="3b51230764da595bb19e8d0962dd8c69ab40dfab"/>.</p>

    <p><bug>66471</bug> was reported publicly on 8 February 2023. The security
       implications were identified by the Tomcat Security team on 9 February
       2023. The issue was made public on 22 March 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.71</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.71" rtext="2023-01-13">
  
    <p><strong>Important: Apache Tomcat denial of service</strong>
       <cve>CVE-2023-24998</cve></p>

    <p>Apache Tomcat uses a packaged renamed copy of Apache Commons FileUpload
       to provide the file upload functionality defined in the Jakarta Servlet
       specification. Apache Tomcat was, therefore, also vulnerable to the
       Apache Commons FileUpload vulnerability <cve>CVE-2023-24998</cve> as
       there was no limit to the number of request parts processed. This
       resulted in the possibility of an attacker triggering a DoS with a
       malicious upload or series of uploads.</p>
       
    <p>This was fixed with commit
       <hashlink hash="cf77cc545de0488fb89e24294151504a7432df74"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team on 11
       December 2022. The issue was made public on 20 February 2023.</p>

    <p>Affects: 9.0.0-M1 to 9.0.70</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.69" rtext="2022-11-14">
  
    <p><strong>Low: Apache Tomcat JsonErrorReportValve injection</strong>
       <cve>CVE-2022-45143</cve></p>

    <p>The <code>JsonErrorReportValve</code> did not escape the
       <code>type</code>, <code>message</code> or <code>description</code>
       values. In some circumstances these are constructed from user provided
       data and it was therefore possible for users to supply values that
       invalidated or manipulated the JSON output.</p>
       
    <p>This was fixed with commit
       <hashlink hash="b336f4e58893ea35114f1e4a415657f723b1298e"/>.</p>

    <p>This issue was identified by the Apache Tomcat Security team on 2
       September 2022. The issue was made public on 3 January 2023.</p>

    <p>Affects: 9.0.40 to 9.0.68</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.68" rtext="2022-10-07">
  
    <p><strong>Low: Apache Tomcat request smuggling</strong>
       <cve>CVE-2022-42252</cve></p>

    <p>If Tomcat was configured to ignore invalid HTTP headers via setting
       <code>rejectIllegalHeader</code> to <code>false</code> (not the default),
       Tomcat did not reject a request containing an invalid
       <code>Content-Length</code> header making a request smuggling attack
       possible if Tomcat was located behind a reverse proxy that also failed to
       reject the request with the invalid header.</p>
       
    <p>This was fixed with commit
       <hashlink hash="4c7f4fd09d2cc1692112ef70b8ee23a7a037ae77"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team on 29
       September 2022. The issue was made public on 31 October 2022.</p>

    <p>Affects: 9.0.0-M1 to 9.0.67</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.65" rtext="2022-07-20">
  
    <p><strong>Low: Apache Tomcat XSS in examples web application</strong>
       <cve>CVE-2022-34305</cve></p>

    <p>The Form authentication example in the examples web application displayed
       user provided data without filtering, exposing a XSS vulnerability.</p>
       
    <p>This was fixed with commit
       <hashlink hash="8b60af90b99945379c2d1003277e0cabc6776bac"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team on 22 June
       2022. The issue was made public on 23 June 2022.</p>

    <p>Affects: 9.0.30 to 9.0.64</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.63" rtext="2022-05-16">
  
    <p><strong>Low: Apache Tomcat EncryptInterceptor DoS</strong>
       <cve>CVE-2022-29885</cve></p>

    <p>The documentation for the EncryptInterceptor incorrectly stated it
        enabled Tomcat clustering to run over an untrusted network. This was not
        correct. While the EncryptInterceptor does provide confidentiality and
        integrity protection, it does not protect against all risks associated
        with running over any untrusted network, particularly DoS risks.</p>
       
    <p>This was fixed with commit
       <hashlink hash="eaafd28296c54d983e28a47953c1f5cb2c334f48"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team by 4ra1n on 17
       April 2022. The issue was made public on 10 May 2022.</p>

    <p>Affects: 9.0.13 to 9.0.62</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.62" rtext="1 April 2022">

    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.61 but the
       release vote for the 9.0.61 release candidate did not pass. Therefore,
       although users must download 9.0.62 to obtain a version that includes a
       fix for these issues, version 9.0.61 is not included in the list of 
       affected versions.</i></p>

    <p><strong>High: Information Disclosure</strong>
       <cve>CVE-2021-43980</cve></p>

    <p>The simplified implementation of blocking reads and writes introduced in
       Tomcat 10 and back-ported to Tomcat 9.0.47 onwards exposed a long
       standing (but extremely hard to trigger) concurrency bug that could cause
       client connections to share an Http11Processor instance resulting in
       responses, or part responses, to be received by the wrong client.</p>
       
    <p>This was fixed with commit
       <hashlink hash="170e0f792bd18ff031677890ba2fe50eb7a376c1"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team by Adam
       Thomas, Richard Hernandez and Ryan Schmitt on 11 November 2021. The issue
       was made public on 28 September 2022.</p>

    <p>Affects: 9.0.0-M1 to 9.0.60</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.58" rtext="20 January 2022">

    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.57 but the
       release vote for the 9.0.57 release candidate did not pass. Therefore,
       although users must download 9.0.58 to obtain a version that includes a
       fix for these issues, version 9.0.57 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Low: Local Privilege Escalation</strong>
       <cve>CVE-2022-23181</cve></p>

    <p>The fix for bug <cve>CVE-2020-9484</cve> introduced a time of check, time
       of use vulnerability that allowed a local attacker to perform actions
       with the privileges of the user that the Tomcat process is using. This
       issue is only exploitable when Tomcat is configured to persist sessions
       using the FileStore.</p>
       
    <p>This was fixed with commit
       <hashlink hash="1385c624b4a1e994426e810075c850edc38a700e"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team by Trung Pham
       of Viettel Cyber Security on 10 December 2021. The issue was made public
       on 26 January 2022.</p>

    <p>Affects: 9.0.35 to 9.0.56</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.54" rtext="1 October 2021">

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2021-42340</cve></p>

    <p>The fix for bug <bug>63362</bug> introduced a memory leak. The object
       introduced to collect metrics for HTTP upgrade connections was not
       released for WebSocket connections once the WebSocket connection was
       closed. This created a memory leak that, over time, could lead to a
       denial of service via an OutOfMemoryError.</p>

    <p>This was fixed with commit
       <hashlink hash="80f1438ec45e77a07b96419808971838d259eb47"/>.</p>

    <p>The memory leak was reported publicly via the users mailing list on 23
       September 2021. The security implications were identified by the Tomcat
       Security team the same day. The issue was made public on 14 October
       2021.</p>

    <p>Affects: 9.0.40 to 9.0.53</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.48" rtext="15 June 2021">

    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.47 but the
       release vote for the 9.0.47 release candidate did not pass. Therefore,
       although users must download 9.0.48 to obtain a version that includes a
       fix for this issue, version 9.0.47 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Important: Request Smuggling</strong>
       <cve>CVE-2021-33037</cve></p>

    <p>Apache Tomcat did not correctly parse the HTTP transfer-encoding request
       header in some circumstances leading to the possibility of request
       smuggling when used with a reverse proxy. Specifically: Tomcat
       incorrectly ignored the transfer-encoding header if the client declared
       it would only accept an HTTP/1.0 response; Tomcat honoured the identify
       encoding; and Tomcat did not ensure that, if present, the chunked
       encoding was the final encoding.</p>

    <p>This was fixed with commits
       <hashlink hash="45d70a86a901cbd534f8f570bed2aec9f7f7b88e"/>,
       <hashlink hash="05f9e8b00f5d9251fcd3c95dcfd6cf84177f46c8"/> and
       <hashlink hash="a2c3dc4c96168743ac0bab613709a5bbdaec41d0"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team by Bahruz
       Jabiyev, Steven Sprecher and Kaan Onarlioglu of NEU seclab on 7 May 2021.
       The issue was made public on 12 July 2021.</p>

    <p>Affects: 9.0.0.M1 to 9.0.46</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.46" rtext="12 May 2021">

      <p><strong>Low: Authentication weakness</strong>
       <cve>CVE-2021-30640</cve></p>

    <p>Queries made by the JNDI Realm did not always correctly escape
       parameters. Parameter values could be sourced from user provided data (eg
       user names) as well as configuration data provided by an administrator.
       In limited circumstances it was possible for users to authenticate using
       variations of their user name and/or to bypass some of the protection
       provided by the LockOut Realm.</p>

    <p>This was fixed with commits
       <hashlink hash="c4df8d44a959a937d507d15e5b1ca35c3dbc41eb"/>,
       <hashlink hash="749f3cc192c68c34f2375509aea087be45fc4434"/>,
       <hashlink hash="c6b6e1015ae44c936971b6bf8bce70987935b92e"/>,
       <hashlink hash="91ecdc61ce3420054c04114baaaf1c1e0cbd5d56"/>,
       <hashlink hash="e50067486cf86564175ca0cfdcbf7d209c6df862"/>,
       <hashlink hash="b5585a9e5d4fec020cc5ebadb82f899fae22bc43"/>,
       <hashlink hash="329932012d3a9b95fde0b18618416e659ecffdc0"/> and
       <hashlink hash="3ce84512ed8783577d9945df28da5a033465b945"/>.</p>

    <p>This issue was reported publicly as <bug>65224</bug>.</p>

    <p>Affects: 9.0.0.M1 to 9.0.45</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.45" rtext="6 April 2021">

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2021-30639</cve></p>

    <p>An error introduced as part of a change to improve error handling during
       non-blocking I/O meant that the error flag associated with the Request
       object was not reset between requests. This meant that once a
       non-blocking I/O error occurred, all future requests handled by that
       request object would fail. Users were able to trigger non-blocking I/O
       errors, e.g. by dropping a connection, thereby creating the possibility
       of triggering a DoS.</p>
    <o>Applications that do not use non-blocking I/O are not exposed to this
       vulnerability.</o>

    <p>This was fixed with commit
       <hashlink hash="8ece47c4a9fb9349e8862c84358a4dd23c643a24"/>.</p>

    <p>This issue was reported publicly as <bug>65203</bug>.</p>

    <p>Affects: 9.0.44</p>
    
  </section>

  <section name="Fixed in Apache Tomcat 9.0.44" rtext="10 March 2021">

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2021-41079</cve></p>

    <p>When Tomcat was configured to use NIO+OpenSSL or NIO2+OpenSSL for TLS, a
      specially crafted packet could be used to trigger an infinite loop
      resulting in a denial of service.</p>

    <p>This was fixed with commit
       <hashlink hash="d4b340fa8feaf55831f9a59350578f7b6ca048b8"/>.</p>

    <p>This issue was first reported to the Apache Tomcat Security Team by
       Thomas Wozenilek on 26 February 2021 but could not be confirmed. A
       speculative fix was applied on 3 March 2021. On 14 September 2021 David
       Frankson of Infinite Campus independently reported the issue and included
       a test case. This allowed both the issue and the speculative fix to be
       verified. The issue was made public on 15 September 2021.</p>
       
    <p>Affects: 9.0.0-M1 to 9.0.43</p>
    
    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2024-21733</cve></p>

    <p>Incomplete POST requests triggered an error response that could contain
       data from a previous request from another user.</p>

    <p>This was fixed with commit
       <hashlink hash="86ccc43940861703c2be96a5f35384407522125a"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by xer0dayz
       from Sn1perSecurity LLC on 20 December 2023. The issue was made public on
       19 January 2024.</p>
       
    <p>Affects: 9.0.0-M11 to 9.0.43</p>
    
  </section>

  <section name="Fixed in Apache Tomcat 9.0.43" rtext="2 February 2021">

    <p><i>Note: The issues below were fixed in Apache Tomcat 9.0.42 but the
       release vote for the 9.0.42 release candidate did not pass. Therefore,
       although users must download 9.0.43 to obtain a version that includes a
       fix for these issues, version 9.0.42 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Low: Fix for <cve>CVE-2020-9484</cve> was incomplete</strong>
       <cve>CVE-2021-25329</cve></p>

    <p>The fix for <cve>CVE-2020-9484</cve> was incomplete. When using a
    highly unlikely configuration edge case, the Tomcat instance was still
    vulnerable to <cve>CVE-2020-9484</cve>. Note that both the previously
    published prerequisites for <cve>CVE-2020-9484</cve> and the previously
    published non-upgrade mitigations for <cve>CVE-2020-9484</cve> also apply to
    this issue.</p>

    <p>This was fixed with commit
       <hashlink hash="4785433a226a20df6acbea49296e1ce7e23de453"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security team by Trung Pham
       of Viettel Cyber Security on 12 January 2021. The issue was made public
       on 1 March 2021.</p>

    <p>Affects: 9.0.0.M1 to 9.0.41</p>

    <p><strong>Important: Request mix-up with h2c</strong>
       <cve>CVE-2021-25122</cve></p>

    <p>When responding to new h2c connection requests, Apache Tomcat could
    duplicate request headers and a limited amount of request body from one
    request to another meaning user A and user B could both see the results of
    user A&apos;s request.</p>

    <p>This was fixed with commit
       <hashlink hash="d47c20a776e8919eaca8da9390a32bc8bf8210b1"/>.</p>

    <p>This issue was identified by the Apache Tomcat Security team on 11
       January 2021. The issue was made public on 1 March 2021.</p>

    <p>Affects: 9.0.0.M1 to 9.0.41</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.40" rtext="17 November 2020">

    <p><strong>Important: Information disclosure</strong>
       <cve>CVE-2021-24122</cve></p>

    <p>When serving resources from a network location using the NTFS file system
       it was possible to bypass security constraints and/or view the source
       code for JSPs in some configurations. The root cause was the unexpected
       behaviour of the JRE API <code>File.getCanonicalPath()</code> which in
       turn was caused by the inconsistent behaviour of the Windows API
       (<code>FindFirstFileW</code>) in some circumstances.
    </p>

    <p>This was fixed with commit
       <hashlink hash="935fc5582dc25ae10bab6f9d5629ff8d996cb533"/>.</p>

    <p>This issue was reported the Apache Tomcat Security team by Ilja Brander
       on 26 October 2020. The issue was made public on 14 January 2021.</p>

    <p>Affects: 9.0.0.M1 to 9.0.39</p>

    <p><strong>Moderate: HTTP/2 request header mix-up</strong>
       <cve>CVE-2020-17527</cve></p>

    <p>While investigating issue <bug>64830</bug> it was discovered that Apache
       Tomcat could re-use an HTTP request header value from the previous stream
       received on an HTTP/2 connection for the request associated with the
       subsequent stream. While this would most likely lead to an error and the
       closure of the HTTP/2 connection, it is possible that information could
       leak between requests.
    </p>

    <p>This was fixed with commit
       <hashlink hash="d56293f816d6dc9e2b47107f208fa9e95db58c65"/>.</p>

    <p>This issue was identified by the Apache Tomcat Security team on 10
       November 2020. The issue was made public on 3 December 2020.</p>

    <p>Affects: 9.0.0-M1 to 9.0.39</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.38" rtext="15 September 2020">

    <p><strong>Moderate: HTTP/2 request mix-up</strong>
       <cve>CVE-2020-13943</cve></p>

    <p>If an HTTP/2 client exceeded the agreed maximum number of concurrent
       streams for a connection (in violation of the HTTP/2 protocol), it was
       possible that a subsequent request made on that connection could contain
       HTTP headers - including HTTP/2 pseudo headers - from a previous request
       rather than the intended headers. This could lead to users seeing
       responses for unexpected resources.</p>

    <p>This was fixed with commit
       <hashlink hash="55911430df13f8c9998fbdee1f9716994d2db59b"/>.</p>

    <p>This issue was identified by the Apache Tomcat Security team on 23 July
       2020. The issue was made public on 12 October 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.37</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.37" rtext="5 July 2020">

    <p><strong>Important: WebSocket DoS</strong>
       <cve>CVE-2020-13935</cve></p>

    <p>The payload length in a WebSocket frame was not correctly validated.
       Invalid payload lengths could trigger an infinite loop. Multiple requests
       with invalid payload lengths could lead to a denial of service.</p>

    <p>This was fixed with commit
       <hashlink hash="40fa74c74822711ab878079d0a69f7357926723d"/>.</p>

    <p>This issue was reported publicly via the Apache Bugzilla instance on 28
       June 2020 and included references to high CPU but no specific reference
       to denial of service. The associated DoS risks were identified by the
       Apache Tomcat Security Team the same day. The issue was made public on 14
       July 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.36</p>

    <p><strong>Moderate: HTTP/2 DoS</strong>
       <cve>CVE-2020-13934</cve></p>

    <p>An h2c direct connection did not release the HTTP/1.1 processor after the
       upgrade to HTTP/2. If a sufficient number of such requests were made, an
       OutOfMemoryException could occur leading to a denial of service.</p>

    <p>This was fixed with commit
       <hashlink hash="172977f04a5215128f1e278a688983dcd230f399"/>.</p>

    <p>This issue was reported publicly via the Apache Tomcat Users mailing list
       on 22 June 2020 without reference to the potential for DoS. After further
       discussion to identify the steps necessary to reproduce the issue, the
       root cause of the issue and the associated DoS risks were identified by
       the Apache Tomcat Security Team on 26 June 2020. The issue was made
       public on 14 July 2020.</p>

    <p>Affects: 9.0.0.M5 to 9.0.36</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.36" rtext="7 June 2020">

    <p><strong>Important: HTTP/2 DoS</strong>
       <cve>CVE-2020-11996</cve></p>

    <p>A specially crafted sequence of HTTP/2 requests could trigger high CPU
       usage for several seconds. If a sufficient number of such requests were
       made on concurrent HTTP/2 connections, the server could become
       unresponsive.</p>

    <p>This was fixed with commit
       <hashlink hash="9a0231683a77e2957cea0fdee88b193b30b0c976"/>.</p>

    <p>This issue was reported publicly via the Apache Tomcat Users mailing list
       on 21 May 2020 without reference to the potential for DoS. The DoS risks
       were identified by the Apache Tomcat Security Team the same day. The
       issue was made  public on 25 June 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.35</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.35" rtext="11 May 2020">

    <p><strong>Important: Remote Code Execution via session persistence</strong>
       <cve>CVE-2020-9484</cve></p>

    <p>If:</p>
    <ul>
      <li>an attacker is able to control the contents and name of a file on the
          server; and</li>
      <li>the server is configured to use the <code>PersistenceManager</code>
          with a <code>FileStore</code>; and</li>
      <li>the <code>PersistenceManager</code> is configured with
          <code>sessionAttributeValueClassNameFilter="null"</code> (the default
          unless a <code>SecurityManager</code> is used) or a sufficiently lax
          filter to allow the attacker provided object to be deserialized;
          and</li>
      <li>the attacker knows the relative file path from the storage location
          used by <code>FileStore</code> to the file the attacker has control
          over;</li>
    </ul>
    <p>then, using a specifically crafted request, the attacker will be able to
       trigger remote code execution via deserialization of the file under their
       control.</p>
       
    <p><strong>Note:</strong> All of conditions above must be true for the
       attack to succeed.</p>

    <p>As an alternative to upgrading to 9.0.35 or later, users may configure
       the <code>PersistenceManager</code> with an appropriate value for
       <code>sessionAttributeValueClassNameFilter</code> to ensure that only
       application provided attributes are serialized and deserialized.</p>

    <p>This was fixed with commit
       <hashlink hash="3aa8f28db7efb311cdd1b6fe15a9cd3b167a2222"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by by jarvis
       threedr3am of pdd security research on 12 April 2020. The issue was made 
       public on 20 May 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.34</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.31" rtext="11 February 2020">

    <p><strong>Important: AJP Request Injection and potential Remote Code Execution</strong>
       <cve>CVE-2020-1938</cve></p>

    <p>When using the Apache JServ Protocol (AJP), care must be taken when
       trusting incoming connections to Apache Tomcat. Tomcat treats AJP
       connections as having higher trust than, for example, a similar HTTP
       connection. If such connections are available to an attacker, they can be
       exploited in ways that may be surprising. Prior to Tomcat 9.0.31, Tomcat
       shipped with an AJP Connector enabled by default that listened on all
       configured IP addresses. It was expected (and recommended in the security
       guide) that this Connector would be disabled if not required.</p>
    <p>Prior to this vulnerability report, the known risks of an attacker being
       able to access the AJP port directly were:</p>
    <ul>
       <li>bypassing security checks based on client IP address</li>
       <li>bypassing user authentication if Tomcat was configured to trust
           authentication data provided by the reverse proxy</li>
       </ul>
    <p>This vulnerability report identified a mechanism that allowed the
       following:</p>
    <ul>
       <li>returning arbitrary files from anywhere in the web application
           including under the WEB-INF and META-INF directories or any other
           location reachable via ServletContext.getResourceAsStream()</li>
       <li>processing any file in the web application as a JSP</li>
    </ul>
    <p>Further, if the web application allowed file upload and stored those
       files within the web application (or the attacker was able to control
       the content of the web application by some other means) then this, along
       with the ability to process a file as a JSP, made remote code execution
       possible.</p>
    <p>It is important to note that mitigation is only required if an AJP port
       is accessible to untrusted users. Users wishing to take a
       defence-in-depth approach and block the vector that permits returning
       arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31
       or later. Users should note that a number of changes were made to the
       default AJP Connector configuration in 9.0.31 to harden the default
       configuration. It is likely that users upgrading to 9.0.31 or later
       will need to make small changes to their configurations as a result.</p>

    <p>This was fixed with commits
       <hashlink hash="0e8a50f0a5958744bea1fd6768c862e04d3b7e75"/>,
       <hashlink hash="9ac90532e9a7d239f90952edb229b07c80a9a3eb"/>,
       <hashlink hash="64fa5b99442589ef0bf2a7fcd71ad2bc68b35fad"/>,
       <hashlink hash="7a1406a3cd20fdd90656add6cd8f27ef8f24e957"/> and
       <hashlink hash="49ad3f954f69c6e838c8cd112ad79aa5fa8e7153"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team on 3 January
       2020. The issue was made public on 24 February 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.30</p>

    <p><strong>Low: HTTP Request Smuggling</strong>
       <cve>CVE-2020-1935</cve></p>

    <p>The HTTP header parsing code used an approach to end-of-line (EOL)
    parsing that allowed some invalid HTTP headers to be parsed as valid. This
    led to a possibility of HTTP Request Smuggling if Tomcat was
    located behind a reverse proxy that incorrectly handled the invalid
    Transfer-Encoding header in a particular manner. Such a reverse proxy is
    considered unlikely.</p>

    <p>This was fixed with commit
       <hashlink hash="8bfb0ff7f25fe7555a5eb2f7984f73546c11aa26"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by @ZeddYu
       on 25 December 2019. The issue was made public on 24
       February 2020.</p>

    <p>Affects: 9.0.0.M1 to 9.0.30</p>

    <p><strong>Low: HTTP Request Smuggling</strong>
       <cve>CVE-2019-17569</cve></p>

    <p>The refactoring in 9.0.28 introduced a regression. The result of the
    regression was that invalid Transfer-Encoding headers were incorrectly
    processed leading to a possibility of HTTP Request Smuggling if Tomcat was
    located behind a reverse proxy that incorrectly handled the invalid
    Transfer-Encoding header in a particular manner. Such a reverse proxy is
    considered unlikely.</p>

    <p>This was fixed with commit
       <hashlink hash="060ecc5eb839208687b7fcc9e35287ac8eb46998"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by @ZeddYu
       on 12 December 2019. The issue was made public on 24
       February 2020.</p>

    <p>Affects: 9.0.28 to 9.0.30</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.30" rtext="12 December 2019">

    <p><strong>Low: Session fixation</strong>
       <cve>CVE-2019-17563</cve></p>

    <p>When using FORM authentication there was a narrow window where an
       attacker could perform a session fixation attack. The window was
       considered too narrow for an exploit to be practical but, erring on the
       side of caution, this issue has been treated as a security
       vulnerability.</p>

    <p>This was fixed with commit
       <hashlink hash="1ecba14e690cf5f3f143eef6ae7037a6d3c16652"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by William
       Marlow (IBM) on 19 November 2019. The issue was made public on 18
       December 2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.29</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.29" rtext="21 November 2019">

    <p><strong>Moderate: Local Privilege Escalation</strong>
       <cve>CVE-2019-12418</cve></p>

    <p>When Tomcat is configured with the JMX Remote Lifecycle Listener, a local
       attacker without access to the Tomcat process or configuration files is
       able to manipulate the RMI registry to perform a man-in-the-middle attack
       to capture user names and passwords used to access the JMX interface. The
       attacker can then use these credentials to access the JMX interface and
       gain complete control over the Tomcat instance.</p>
    <p>The JMX Remote Lifecycle Listener will be deprecated in future Tomcat
       releases, will be removed for Tomcat 10 and may be removed from all
       Tomcat releases some time after 31 December 2020.</p>
    <p>Users should also be aware of <cve>CVE-2019-2684</cve>, a JRE
       vulnerability that enables this issue to be exploited remotely.</p>

    <p>This was fixed with commit
       <hashlink hash="1fc9f589dbdd8295cf313b2667ab041c425f99c3"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by An Trinh of
       Viettel Cyber Security on 10 October 2019. The issue was made public on 18
       December 2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.28</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.21" rtext="7 June 2019">

    <p><strong>Important: Request mix-up</strong>
       <cve>CVE-2022-25762</cve></p>

    <p>If a web application sends a WebSocket message concurrently with the
       WebSocket connection closing, it is possible that the application will
       continue to use the socket after it has been closed. The error handling
       triggered in this case could cause the a pooled object to be placed in
       the pool twice. This could result in subsequent connections using the
       same object concurrently which could result in data being returned to the
       wrong use and/or other errors.</p>

    <p>This was fixed with commits
       <hashlink hash="e2d5a040b962a904db5264b3cb3282c6b05f823c"/>,
       <hashlink hash="7046644bf361b89afc246b6643e24ce2ae60cacc"/>,
       <hashlink hash="339b40bc07bdba9ded565929b9a3448c5a78f015"/> and
       <hashlink hash="65fb1ee548111021edde247f3b3c409ec95a5183"/>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 21
       December 2021. The issue was made public on 12 May 2022.</p>

    <p>Affects: 9.0.0.M1 to 9.0.20</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.20" rtext="13 May 2019">

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2019-10072</cve></p>

    <p>The fix for <cve>CVE-2019-0199</cve> was incomplete and did not address
       HTTP/2 connection window exhaustion on write. By not sending
       WINDOW_UPDATE messages for the connection window (stream 0) clients were
       able to cause server-side threads to block eventually leading to thread
       exhaustion and a DoS.</p>

    <p>This was fixed with commits
       <hashlink hash="7f748eb6bfaba5207c89dbd7d5adf50fae847145"/> and
       <hashlink hash="ada725a50a60867af3422c8e612aecaeea856a9a"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by John
       Simpson of Trend Micro Security Research working with Trend Micro's Zero
       Day Initiative on 26 April 2019. The issue was made public on 20 June
       2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.19</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.19" rtext="13 April 2019">

    <p><i>Note: The issues below were fixed in Apache Tomcat 9.0.18 but the
       release vote for the 9.0.18 release candidate did not pass. Therefore,
       although users must download 9.0.19 to obtain a version that includes a
       fix for these issues, version 9.0.18 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Important: Remote Code Execution on Windows</strong>
       <cve>CVE-2019-0232</cve></p>

    <p>When running on Windows with enableCmdLineArguments enabled, the CGI
       Servlet is vulnerable to Remote Code Execution due to a bug in the way
       the JRE passes command line arguments to Windows. The CGI Servlet is
       disabled by default. The CGI option enableCmdLineArguments is disabled by
       default in Tomcat 9.0.x. For a detailed explanation of the JRE behaviour,
       see
       <a href="https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html">Markus
       Wulftange's blog</a> and this archived
       <a href="https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/">MSDN
       blog</a>.</p>

    <p>This was fixed with commit
       <hashlink hash="4b244d827ade2a36ef3b8734939541207b78f35c"/>.</p>

    <p>This issue was identified by Nightwatch Cybersecurity Research and
       reported to the Apache Tomcat security team via the bug bounty program
       sponsored by the EU FOSSA-2 project on 3rd March 2019. The issue was made
       public on 10 April 2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.17</p>

    <p><strong>Low: XSS in SSI printenv</strong>
       <cve>CVE-2019-0221</cve></p>

    <p>The SSI printenv command echoes user provided data without escaping and
       is, therefore, vulnerable to XSS. SSI is disabled by default. The
       printenv command is intended for debugging and is unlikely to be present
       in a production website.</p>

    <p>This was fixed with commit
       <hashlink hash="15fcd166ea2c1bb79e8541b8e1a43da9c452ceea"/>.</p>

    <p>This issue was identified by Nightwatch Cybersecurity Research and
       reported to the Apache Tomcat security team via the bug bounty program
       sponsored by the EU FOSSA-2 project on 7th March 2019. The issue was made
       public on 17 May 2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.17</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.16" rtext="8 February 2019">
  
    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.15 but the
       release vote for the 9.0.15 release candidate did not pass. Therefore,
       although users must download 9.0.16 to obtain a version that includes a
       fix for these issues, version 9.0.15 is not included in the list of 
       affected versions.</i></p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2019-0199</cve></p>

    <p>The HTTP/2 implementation accepted streams with excessive numbers of
       <code>SETTINGS</code> frames and also permitted clients to keep streams
       open without reading/writing request/response data. By keeping streams
       open for requests that utilised the Servlet API's blocking I/O, clients
       were able to cause server-side threads to block eventually leading to
       thread exhaustion and a DoS.</p>

    <p>This was fixed in revisions <revlink rev="1852698">1852698</revlink>,
       <revlink rev="1852699">1852699</revlink>,
       <revlink rev="1852700">1852700</revlink>,
       <revlink rev="1852701">1852701</revlink>,
       <revlink rev="1852702">1852702</revlink>,
       <revlink rev="1852703">1852703</revlink>,
       <revlink rev="1852704">1852704</revlink>,
       <revlink rev="1852705">1852705</revlink>,
       <revlink rev="1852706">1852706</revlink> and
       <hashlink hash="a1cb1ac77e3a8fec1b00eb0e944842555da14f7d"/>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by Michal Karm
       Babacek from Red Hat, Inc on 4 January 2019 with additional issues
       identified by the Tomcat Security Team. The issue was made public on 25
       March 2019.</p>

    <p>Affects: 9.0.0.M1 to 9.0.14</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.12" rtext="10 September 2018">
  
    <p><strong>Moderate: Open Redirect</strong>
       <cve>CVE-2018-11784</cve></p>

    <p>When the default servlet returned a redirect to a directory (e.g.
       redirecting to <code>/foo/</code> when the user requested
       <code>/foo</code>) a specially crafted URL could be used to cause the
       redirect to be generated to any URI of the attackers choice.</p>

    <p>This was fixed in revision <revlink rev="1840055">1840055</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by Sergey
       Bobrov on 28 August 2018 and made public on 3 October 2018.</p>

    <p>Affects: 9.0.0.M1 to 9.0.11</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.10" rtext="25 June 2018">

    <p><strong>Low: host name verification missing in WebSocket client</strong>
       <cve>CVE-2018-8034</cve></p>

    <p>The host name verification when using TLS with the WebSocket client was
       missing. It is now enabled by default.</p>

    <p>This was fixed in revision <revlink rev="1833757">1833757</revlink>.</p>

    <p>This issue was reported publicly on 11 June 2018 and formally announced as
       a vulnerability on 22 July 2018.</p>

    <p>Affects: 9.0.0.M1 to 9.0.9</p>

    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2018-8037</cve></p>

    <p>If an async request was completed by the application at the same time as
       the container triggered the async timeout, a race condition existed that
       could result in a user seeing a response intended for a different user.
       An additional issue was present in the NIO and NIO2 connectors that did
       not correctly track the closure of the connection when an async request
       was completed by the application and timed out by the container at the
       same time. This could also result in a user seeing a response intended
       for another user.</p>

    <p>This was fixed in revisions <revlink rev="1833825">1833825</revlink>,
       <revlink rev="1833831">1833831</revlink>,
       <revlink rev="1837530">1837530</revlink> and
       <revlink rev="1833906">1833906</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by Dmitry
       Treskunov on 16 June 2018 and made public on 22 July 2018.</p>

    <p>Affects: 9.0.0.M9 to 9.0.9</p>

  </section>
  <section name="Fixed in Apache Tomcat 9.0.9" rtext="not released">
  
    <p><strong>Low: CORS filter has insecure defaults</strong>
       <cve>CVE-2018-8014</cve></p>

    <p>The defaults settings for the CORS filter are insecure and enable
       <code>supportsCredentials</code> for all origins. It is expected that
       users of the CORS filter will have configured it appropriately for their
       environment rather than using it in the default configuration. Therefore,
       it is expected that most users will not be impacted by this issue.</p>

    <p>This was fixed in revision <revlink rev="1831726">1831726</revlink>.</p>

    <p>This issue was reported publicly on 1 May 2018 and formally announced as
       a vulnerability on 16 May 2018.</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.8" rtext="3 May 2018">

    <p><strong>Important: A bug in the UTF-8 decoder can lead to DoS</strong>
       <cve>CVE-2018-1336</cve></p>
 
    <p>An improper handing of overflow in the UTF-8 decoder with
       supplementary characters can lead to an infinite loop in the
       decoder causing a Denial of Service.</p>

    <p>This was fixed in revision <revlink rev="1830373">1830373</revlink>.</p>

    <p>This issue was reported publicly on 6 April 2018 and formally announced as
       a vulnerability on 22 July 2018.</p>

    <p>Affects: 9.0.0.M1 to 9.0.7</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.5" rtext="11 February 2018">
  
    <p><strong>Important: Security constraint annotations applied too
       late</strong> <cve>CVE-2018-1305</cve></p>

    <p>Security constraints defined by annotations of Servlets were only applied
       once a Servlet had been loaded. Because security constraints defined in
       this way apply to the URL pattern and any URLs below that point, it was
       possible - depending on the order Servlets were loaded - for some
       security constraints not to be applied. This could have exposed resources
       to users who were not authorised to access them.</p>

    <p>This was fixed in revisions <revlink rev="1823310">1823310</revlink> and
       <revlink rev="1824323">1824323</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security on 1 February
       2018 and made public on 23 February 2018.</p>

    <p>Affects: 9.0.0.M1 to 9.0.4</p>

    <p><strong>Important: Security constraints mapped to context root are
       ignored</strong> <cve>CVE-2018-1304</cve></p>

    <p>The URL pattern of "" (the empty string) which exactly maps to the
       context root was not correctly handled when used as part of a security
       constraint definition. This caused the constraint to be ignored. It was,
       therefore, possible for unauthorised users to gain access to web
       application resources that should have been protected. Only security
       constraints with a URL pattern of the empty string were affected.</p>

    <p>This was fixed in revision <revlink rev="1823306">1823306</revlink>.</p>

    <p>This issue was reported publicly as <bug>62067</bug> on 31 January 2018
       and the security implications identified by the Apache Tomcat Security
       Team the same day. It was made public on 23 February 2018.</p>

    <p>Affects: 9.0.0.M1 to 9.0.4</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.2" rtext="30 November 2017">

    <p><strong>Low: Incorrectly documented CGI search algorithm</strong>
       <cve>CVE-2017-15706</cve></p>

    <p>As part of the fix for bug <bug>61201</bug>, the description of the
       search algorithm used by the CGI Servlet to identify which script to
       execute was updated. The update was not correct. As a result, some
       scripts may have failed to execute as expected and other scripts may have
       been executed unexpectedly. Note that the behaviour of the CGI servlet
       has remained unchanged in this regard. It is only the documentation of
       the behaviour that was wrong and has been corrected.</p>

    <p>This was fixed in revision <revlink rev="1814825">1814825</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by Jan Michael
       Greiner on 17 September 2017 and made public on 31 January 2018.</p>

    <p>Affects: 9.0.0.M22 to 9.0.1</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.1" rtext="30 September 2017">

    <p><strong>Important: Remote Code Execution</strong>
       <cve>CVE-2017-12617</cve></p>

    <p>When running with HTTP PUTs enabled (e.g. via setting the
       <code>readonly</code> initialisation parameter of the Default servlet to
       false) it was possible to upload a JSP file to the server via a specially
       crafted request. This JSP could then be requested and any code it
       contained would be executed by the server.</p>

    <p>This was fixed in revisions <revlink rev="1809669">1809669</revlink>,
       <revlink rev="1809674">1809674</revlink>,
       <revlink rev="1809684">1809684</revlink> and
       <revlink rev="1809711">1809711</revlink>.</p>

    <p>This issue was first reported publicly followed by multiple reports to
       the Apache Tomcat Security Team on 20 September 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.0.M22" rtext="26 June 2017">

    <p><strong>Important: Security Constraint Bypass</strong>
       <cve>CVE-2017-7675</cve></p>

    <p>The HTTP/2 implementation bypassed a number of security checks that
       prevented directory traversal attacks. It was therefore possible to
       bypass security constraints using an specially crafted URL.</p>

    <p>This was fixed in revision <revlink rev="1796090">1796090</revlink>.</p>

    <p>The issue was originally reported as a failure to process URL path
       parameters in bug <bug>61120</bug> on 24 May 2017. The full implications
       of this issue were identified by the Tomcat Security Team the same day.
       This issue was made public on 10 August 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M21</p>

    <p><strong>Moderate: Cache Poisoning</strong>
       <cve>CVE-2017-7674</cve></p>

    <p>The CORS Filter did not add an HTTP Vary header indicating that the
       response varies depending on Origin. This permitted client and server
       side cache poisoning in some circumstances.</p>

    <p>This was fixed in revision <revlink rev="1795813">1795813</revlink>.</p>

    <p>The issue was reported as bug <bug>61101</bug> on 16 May 2017. The full
       implications of this issue were identified by the Tomcat Security Team
       the same day. This issue was made public on 10 August 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M21</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.0.M21" rtext="10 May 2017">
  
    <p><strong>Important: Security Constraint Bypass</strong>
       <cve>CVE-2017-5664</cve></p>

    <p>The error page mechanism of the Java Servlet Specification requires that,
       when an error occurs and an error page is configured for the error that
       occurred, the original request and response are forwarded to the error
       page. This means that the request is presented to the error page with the
       original HTTP method.</p>

   <p>If the error page is a static file, expected behaviour is to serve content
      of the file as if processing a GET request, regardless of the actual HTTP
      method. Tomcat's Default Servlet did not do this. Depending on the
      original request this could lead to unexpected and undesirable results for
      static error pages including, if the DefaultServlet is configured to
      permit writes, the replacement or removal of the custom error page.</p>

    <p>Notes for other user provided error pages:</p>
    <ul>
      <li>Unless explicitly coded otherwise, JSPs ignore the HTTP method.
          JSPs used as error pages must ensure that they handle any error
          dispatch as a GET request, regardless of the actual method.</li>
      <li>By default, the response generated by a Servlet does depend on the
          HTTP method. Custom Servlets used as error pages must ensure that
          they handle any error dispatch as a GET request, regardless of the
          actual method.</li>
    </ul>

    <p>This was fixed in revisions <revlink rev="1793468">1793468</revlink> and
       <revlink rev="1793487">1793487</revlink>.</p>

    <p>This issue was reported responsibly to the Apache Tomcat Security Team by
       Aniket Nandkishor Kulkarni from Tata Consultancy Services Ltd, Mumbai,
       India as a vulnerability that allowed the restrictions on OPTIONS and
       TRACE requests to be bypassed on 21 April 2017. The full implications of
       this issue were identified by the Tomcat Security Team on 24 April 2017.
       This issue was made public on 6 June 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M20</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M19" rtext="30 March 2017">

    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2017-5651</cve></p>

    <p>The refactoring of the HTTP connectors for 8.5.x onwards, introduced a
       regression in the send file processing. If the send file processing
       completed quickly, it was possible for the Processor to be added to the
       processor cache twice. This could result in the same Processor being used
       for multiple requests which in turn could lead to unexpected errors
       and/or response mix-up.</p>

    <p>This was fixed in revision <revlink rev="1788544">1788544</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 24
       March 2017 and made public on 10 April 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M18</p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2017-5650</cve></p>

    <p>The handling of an HTTP/2 GOAWAY frame for a connection did not close
       streams associated with that connection that were currently waiting for a
       WINDOW_UPDATE before allowing the application to write more data. These
       waiting streams each consumed a thread. A malicious client could
       therefore construct a series of HTTP/2 requests that would consume all
       available processing threads.</p>

    <p>This was fixed in revision <revlink rev="1788460">1788460</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team by Chun Han
       Hsiao on 11 March 2017 and made public on 10 April 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M18</p>

  <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2017-5647</cve></p>

    <p>A bug in the handling of the pipelined requests when send file was used
       resulted in the pipelined request being lost when send file processing of
       the previous request completed. This could result in responses appearing
       to be sent for the wrong request. For example, a user agent that sent
       requests A, B and C could see the correct response for request A, the
       response for request C for request B and no response for request C.</p>

    <p>This was fixed in revision <revlink rev="1788890">1788890</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 20
       March 2017 and made public on 10 April 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M18</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M18" rtext="13 March 2017">

  <p><strong>Low: Information Disclosure</strong>
       <cve>CVE-2017-5648</cve></p>

    <p>While investigating bug 60718, it was noticed that some calls to
       application listeners did not use the appropriate facade object. When
       running an untrusted application under a SecurityManager, it was
       therefore possible for that untrusted application to retain a reference
       to the request or response object and thereby access and/or modify
       information associated with another web application.</p>

    <p>This was fixed in revision <revlink rev="1785774">1785774</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 20
       March 2017 and made public on 10 April 2017.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M17</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M17" rtext="16 January 2017">

    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.0.M16 but the
       release vote for the 9.0.0.M16 release candidate did not pass. Therefore,
       although users must download 9.0.0.M17 to obtain a version that includes
       the fix for this issue, version 9.0.0.M16 is not included in the list of
       affected versions.</i></p>

  <p><strong>Moderate: Information Disclosure</strong>
       <cve>CVE-2016-8747</cve></p>

    <p>The refactoring to make wider use of ByteBuffer introduced a regression
       that could cause information to leak between requests on the same
       connection. When running behind a reverse proxy, this could result in
       information leakage between users. All HTTP connector variants are
       affected but HTTP/2 and AJP are not affected.</p>

    <p>This was fixed in revision <revlink rev="1774161">1774161</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 14
       December 2016 and made public on 13 March 2017.</p>

    <p>Affects: 9.0.0.M11 to 9.0.0.M15</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M15" rtext="8 December 2016">

    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.0.M14 but the
       release vote for the 9.0.0.M14 release candidate did not pass. Therefore,
       although users must download 9.0.0.M15 to obtain a version that includes
       the fix for this issue, version 9.0.0.M14 is not included in the list of
       affected versions.</i></p>
  
    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2016-8745</cve></p>

    <p>A bug in the error handling of the send file code for the NIO HTTP
       connector resulted in the current Processor object being added to the
       Processor cache multiple times. This in turn meant that the same
       Processor could be used for concurrent requests. Sharing a Processor can
       result in information leakage between requests including, but not limited
       to, session ID and the response body.</p>

    <p>This was fixed in revision <revlink rev="1771853">1771853</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 8 December
       2016 and made public on 12 December 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M13</p>

  </section>

  <section name="Fixed in Apache Tomcat 9.0.0.M13" rtext="8 November 2016">

    <p><i>Note: The issues below were fixed in Apache Tomcat 9.0.0.M12 but the
       release vote for the 9.0.0.M12 release candidate did not pass. Therefore,
       although users must download 9.0.0.M13 to obtain a version that includes
       fixes for these issues, version 9.0.0.M12 is not included in the list of
       affected versions.</i></p>
  
    <p><strong>Important: Remote Code Execution</strong>
       <cve>CVE-2016-8735</cve></p>

    <p>The <code>JmxRemoteLifecycleListener</code> was not updated to take
       account of Oracle's fix for <cve>CVE-2016-3427</cve>. Therefore, Tomcat
       installations using this listener remained vulnerable to a similar remote
       code execution vulnerability. This issue has been rated as important
       rather than critical due to the small number of installations using this
       listener and that it would be highly unusual for the JMX ports to be
       accessible to an attacker even when the listener is used.</p>

    <p>This was fixed in revision <revlink rev="1767644">1767644</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team on 19 October
       2016 and made public on 22 November 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M11</p>

    <p><strong>Important: Denial of Service</strong>
       <cve>CVE-2016-6817</cve></p>

    <p>The HTTP/2 header parser entered an infinite loop if a header was
       received that was larger than the available buffer. This made a denial of
       service attack possible.</p>

    <p>This was fixed in revision <revlink rev="1765794">1765794</revlink>.</p>

    <p>This issue was reported as <bug>60232</bug> on 10 October 2016 and the
       security implications identified by the Apache Tomcat Security Team on
       the same day. It was made public on 22 November 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M11</p>

    <p><strong>Important: Information Disclosure</strong>
       <cve>CVE-2016-6816</cve></p>

    <p>The code that parsed the HTTP request line permitted invalid characters.
       This could be exploited, in conjunction with a proxy that also permitted
       the invalid characters but with a different interpretation, to inject
       data into the HTTP response. By manipulating the HTTP response the
       attacker could poison a web-cache, perform an XSS attack and/or obtain
       sensitive information from requests other then their own.</p>

    <p>This was fixed in revision <revlink rev="1767641">1767641</revlink>.</p>

    <p>This issue was reported to the Apache Tomcat Security Team on 11 October
       2016 and made public on 22 November 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M11</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M10" rtext="5 September 2016">

    <p><strong>Low: Unrestricted Access to Global Resources</strong>
       <cve>CVE-2016-6797</cve></p>

    <p>The ResourceLinkFactory did not limit web application access to global
       JNDI resources to those resources explicitly linked to the web
       application. Therefore, it was possible for a web application to access
       any global JNDI resource whether an explicit ResourceLink had been
       configured or not.</p>

    <p>This was fixed in revision <revlink rev="1757271">1757271</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 18
       January 2016 and made public on 27 October 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M9</p>

    <p><strong>Low: Security Manager Bypass</strong>
       <cve>CVE-2016-6796</cve></p>

    <p>A malicious web application was able to bypass a configured
       SecurityManager via manipulation of the configuration parameters for the
       JSP Servlet.</p>

    <p>This was fixed in revisions <revlink rev="1758487">1758487</revlink> and
       <revlink rev="1763232">1763232</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 27
       December 2015 and made public on 27 October 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M9</p>

    <p><strong>Low: System Property Disclosure</strong>
       <cve>CVE-2016-6794</cve></p>

    <p>When a SecurityManager is configured, a web application's ability to read
       system properties should be controlled by the SecurityManager. Tomcat's
       system property replacement feature for configuration files could be used
       by a malicious web application to bypass the SecurityManager and read
       system properties that should not be visible.</p>

    <p>This was fixed in revision <revlink rev="1754445">1754445</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 27
       December 2015 and made public on 27 October 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M9</p>

    <p><strong>Low: Security Manager Bypass</strong>
       <cve>CVE-2016-5018</cve></p>

    <p>A malicious web application was able to bypass a configured
       SecurityManager via a Tomcat utility method that was accessible to web
       applications.</p>

    <p>This was fixed in revisions <revlink rev="1754714">1754714</revlink> and
       <revlink rev="1760300">1760300</revlink>.</p>

    <p>This issue was discovered by Alvaro Munoz and Alexander Mirosh of the HP
       Enterprise Security Team and reported to the Apache Tomcat Security Team
       on 5 July 2016. It was made public on 27 October 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M9</p>

    <p><strong>Low: Timing Attack</strong>
       <cve>CVE-2016-0762</cve></p>

    <p>The Realm implementations did not process the supplied password if the
       supplied user name did not exist. This made a timing attack possible to
       determine valid user names. Note that the default configuration includes
       the LockOutRealm which makes exploitation of this vulnerability
       harder.</p>

    <p>This was fixed in revision <revlink rev="1758499">1758499</revlink>.</p>

    <p>This issue was identified by the Apache Tomcat Security Team on 1 January
       2016 and made public on 27 October 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M9</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M8" rtext="13 June 2016">
  
    <p><i>Note: The issue below was fixed in Apache Tomcat 9.0.0.M7 but the
       release vote for the 9.0.0.M7 release candidate did not pass. Therefore,
       although users must download 9.0.0.M8 to obtain a version that includes
       fixes for these issues, version 9.0.0.M7 is not included in the list of
       affected versions.</i></p>
  
    <p><strong>Moderate: Denial of Service</strong>
       <cve>CVE-2016-3092</cve></p>

    <p>Apache Tomcat uses a package renamed copy of Apache Commons FileUpload to
       implement the file upload requirements of the Servlet specification. A
       denial of service vulnerability was identified in Commons FileUpload that
       occurred when the length of the multipart boundary was just below the
       size of the buffer (4096 bytes) used to read the uploaded file. This
       caused the file upload process to take several orders of magnitude
       longer than if the boundary was the typical tens of bytes long.</p>

    <p>This was fixed in revision <revlink rev="1743700">1743700</revlink>.</p>

    <p>This issue was identified by the TERASOLUNA Framework Development Team
       and reported to the Apache Commons team via JPCERT on 9 May 2016. It was
       made public on 21 June 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M6</p>

  </section>
  
  <section name="Fixed in Apache Tomcat 9.0.0.M3" rtext="5 January 2016">
  
    <p><strong>Moderate: Security Manager bypass</strong>
       <cve>CVE-2016-0763</cve></p>

    <p>This issue only affects users running untrusted web applications under a
       security manager.</p>
       
    <p><code>ResourceLinkFactory.setGlobalContext()</code> is a public method
       and was accessible to web applications even when running under a security
       manager. This allowed a malicious web application to inject a malicious
       global context that could in turn be used to disrupt other web
       applications and/or read and write data owned by other web
       applications.</p>

    <p>This was fixed in revision <revlink rev="1725926">1725926</revlink>.</p>

    <p>This issue was identified by the Tomcat security team on 18 January 2016
       and made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1 to 9.0.0.M2</p>

  <p><i>Note: The issues below were fixed in Apache Tomcat 9.0.0.M2 but the
       release vote for the 9.0.0.M2 release candidate did not pass. Therefore,
       although users must download 9.0.0.M3 to obtain a version that includes
       fixes for these issues, version 9.0.0.M2 is not included in the list of
       affected versions.</i></p>

    <p><strong>Low: Directory disclosure</strong>
       <cve>CVE-2015-5345</cve></p>

    <p>When accessing a directory protected by a security constraint with a URL
       that did not end in a slash, Tomcat would redirect to the URL with the
       trailing slash thereby confirming the presence of the directory before
       processing the security constraint. It was therefore possible for a user
       to determine if a directory existed or not, even if the user was not
       permitted to view the directory. The issue also occurred at the root of a
       web application in which case the presence of the web application was
       confirmed, even if a user did not have access.</p>

    <p>The solution was to implement the redirect in the DefaultServlet so that
       any security constraints and/or security enforcing Filters were processed
       before the redirect. The Tomcat team recognised that moving the redirect
       could cause regressions so two new Context configuration options
       (<code>mapperContextRootRedirectEnabled</code> and
       <code>mapperDirectoryRedirectEnabled</code>) were introduced. The initial
       default was <code>false</code> for both since this was more secure. 
       However, due to regressions such as
       <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=58765">Bug
       58765</a> the default for <code>mapperContextRootRedirectEnabled</code>
       was later changed to true since it was viewed that the regression was
       more serious than the security risk of associated with being able to
       determine if a web application was deployed at a given path.</p>

    <p>This was fixed in revisions <revlink rev="1715206">1715206</revlink>,
       <revlink rev="1716882">1716882</revlink> and
       <revlink rev="1716894">1716894</revlink>.</p>

    <p>This issue was identified by Mark Koek of QCSec on 12 October 2015 and
    made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1</p>

    <p><strong>Low: Session Fixation</strong>
       <cve>CVE-2015-5346</cve></p>

    <p>When recycling the <code>Request</code> object to use for a new request,
    the <code>requestedSessionSSL</code> field was not recycled. This meant that
    a session ID provided in the next request to be processed using the recycled
    <code>Request</code> object could be used when it should not have been. This
    gave the client the ability to control the session ID. In theory, this could
    have been used as part of a session fixation attack but it would have been
    hard to achieve as the attacker would not have been able to force the victim
    to use the 'correct' <code>Request</code> object. It was also necessary for
    at least one web application to be configured to use the SSL session ID as
    the HTTP session ID. This is not a common configuration.</p>

    <p>This was fixed in revisions <revlink rev="1713184">1713184</revlink> and
       <revlink rev="1723414">1723414</revlink>.</p>

    <p>This issue was identified by the Tomcat security team on 22 June 2014
       and made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1</p>

    <p><strong>Moderate: CSRF token leak</strong>
       <cve>CVE-2015-5351</cve></p>

    <p>The index page of the Manager and Host Manager applications included a
       valid CSRF token when issuing a redirect as a result of an
       unauthenticated request to the root of the web application. If an
       attacker had access to the Manager or Host Manager applications
       (typically these applications are only accessible to internal users, not
       exposed to the Internet), this token could then be used by the attacker
       to construct a CSRF attack.</p>

    <p>This was fixed in revisions <revlink rev="1720652">1720652</revlink> and
       <revlink rev="1720655">1720655</revlink>.</p>

    <p>This issue was identified by the Tomcat security team on 8 December 2015
       and made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1</p>

    <p><strong>Low: Security Manager bypass</strong>
       <cve>CVE-2016-0706</cve></p>

    <p>This issue only affects users running untrusted web applications under a
       security manager.</p>
       
    <p>The internal StatusManagerServlet could be loaded by a malicious web
       application when a security manager was configured. This servlet could
       then provide the malicious web application with a list of all deployed
       applications and a list of the HTTP request lines for all requests
       currently being processed. This could have exposed sensitive information
       from other web applications, such as session IDs, to the web
       application.</p>

    <p>This was fixed in revision <revlink rev="1722799">1722799</revlink>.</p>

    <p>This issue was identified by the Tomcat security team on 27 December 2015
       and made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1</p>

    <p><strong>Moderate: Security Manager bypass</strong>
       <cve>CVE-2016-0714</cve></p>

    <p>This issue only affects users running untrusted web applications under a
       security manager.</p>
       
    <p>Tomcat provides several session persistence mechanisms. The
       <code>StandardManager</code> persists session over a restart. The
       <code>PersistentManager</code> is able to persist sessions to files, a
       database or a custom <code>Store</code>. The cluster implementation
       persists sessions to one or more additional nodes in the cluster. All of
       these mechanisms could be exploited to bypass a security manager. Session
       persistence is performed by Tomcat code with the permissions assigned to
       Tomcat internal code. By placing a carefully crafted object into a
       session, a malicious web application could trigger the execution of
       arbitrary code.</p>

    <p>This was fixed in revisions <revlink rev="1725263">1725263</revlink> and
       <revlink rev="1725914">1725914</revlink>.</p>

    <p>This issue was identified by the Tomcat security team on 12 November 2015
       and made public on 22 February 2016.</p>

    <p>Affects: 9.0.0.M1</p>

  </section>

  <section name="Not a vulnerability in Tomcat">

    <p><strong>Critical: Remote Code Execution via log4j</strong>
       <cve>CVE-2021-44228</cve></p>

    <p>Apache Tomcat 9.0.x has no dependency on any version of log4j.</p>
    
    <p>Web applications deployed on Apache Tomcat may have a dependency on
       log4j. You should seek support from the application vendor in this
       instance.</p>
    
    <p>It is possible to configure Apache Tomcat 9.0.x to use log4j 2.x for
       Tomcat's internal logging. This requires explicit configuration and the
       addition of the log4j 2.x library. Anyone who has switched Tomcat's
       internal logging to log4j 2.x is likely to need to address this
       vulnerability.</p>
   
    <p>In most cases, disabling the problematic feature will be the simplest
       solution. Exactly how to do that depends on the exact version of log4j
       2.x being used. Details are provided on the
       <a href="https://logging.apache.org/log4j/2.x/security.html">log4j 2.x
       security page</a>.</p>

  </section>
  
</body>
</document>

