CVE-2025-53506: Apache Tomcat: DoS via excessive h2 streams at connection start

Published Jul 10, 2025
·
Updated

CVE-2025-52434Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Tomcat when using the APR/Native connector. This was particularly noticeable with client initiated closes of HTTP/2 connections. This issue affects Apache Tomcat: from 9.0.0.M1 through 9.0.106. Users are recommended to upgrade to version 9.0.107, which fixes the issue. CVE-2025-53506Uncontrolled Resource Consumption vulnerability in Apache Tomcat if an HTTP/2 client did not acknowledge the initial settings frame that reduces the maximum permitted concurrent streams. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.8, from 10.1.0-M1 through 10.1.42, from 9.0.0.M1 through 9.0.106. Users are recommended to upgrade to version 11.0.9, 10.1.43 or 9.0.107, which fix the issue.

Other sources

Uncontrolled Resource Consumption vulnerability in Apache Tomcat if an HTTP/2 client did not acknowledge the initial settings frame that reduces the maximum permitted concurrent streams.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.8, from 10.1.0-M1 through 10.1.42, from 9.0.0.M1 through 9.0.106. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100. Other EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.9, 10.1.43 or 9.0.107, which fix the issue.

NVD

Affected Software

9 affected componentsFixes available
Apache Tomcat>=undefined
maven/org.apache.tomcat:tomcat-coyote>=9.0.0.M1<9.0.107
9.0.107
maven/org.apache.tomcat:tomcat-coyote>=10.1.0-M1<10.1.43
10.1.43
maven/org.apache.tomcat:tomcat-coyote>=11.0.0-M1<11.0.9
11.0.9
F5 Traffix SDC=5.2.0
Apache Tomcat>=9.0.0<=9.0.106
Apache Tomcat>=10.1.0<=10.1.42
Apache Tomcat>=11.0.0<=11.0.8
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 9.0.107
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 10.1.43
  3. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 11.0.9
  4. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.9
  5. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.43
  6. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.107

Event History

Jul 10, 2025
CVE Published
via MITRE·07:14 PM
Data Sourced
via MITRE·07:14 PM
DescriptionWeakness
Data Sourced
via Red Hat·08:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
Affected Software
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionSeverityWeaknessAffected Software
Aug 7, 2025
Advisory Published
via F5·04:57 PM
Data Sourced
via F5·04:57 PM
DescriptionSeverityWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-53506?

CVE-2025-53506 is classified as a medium severity vulnerability due to the potential for resource exhaustion.

2

How do I fix CVE-2025-53506?

To fix CVE-2025-53506, upgrade Apache Tomcat to a version beyond 11.0.8, 10.1.42, or 9.0.106.

3

What products are affected by CVE-2025-53506?

CVE-2025-53506 affects Apache Tomcat versions from 11.0.0-M1 to 11.0.8, 10.1.0-M1 to 10.1.42, and 9.0.0-M1 to 9.0.106.

4

What is the nature of the vulnerability described in CVE-2025-53506?

CVE-2025-53506 is an uncontrolled resource consumption vulnerability that can occur if an HTTP/2 client fails to acknowledge the initial settings frame.

5

Can CVE-2025-53506 lead to a denial of service?

Yes, CVE-2025-53506 can potentially lead to denial of service due to excessive resource consumption by the vulnerable instance.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203