# CVE-2024-34750: Apache Tomcat: HTTP/2 excess header handling DoS > Attackers can cause denial of service in Apache Tomcat by exploiting improper HTTP/2 header handling that keeps connections open indefinitely. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Jul 2024 - **Updated:** 3 Nov 2025 - **Also known as:** ALSA-2024:5693, ALSA-2024:5694, BIT-tomcat-2024-34750, CLSA-2025-1737993258, CLSA-2026-1779238039, DEBIAN-CVE-2024-34750, GHSA-wm9w-rjj3-j356, MGASA-2024-0267, RLSA-2024:5693, RLSA-2024:5694, ROOT-APP-MAVEN-CVE-2024-34750, SUSE-SU-2024:2413-1, SUSE-SU-2024:2485-1, SUSE-SU-2024:2539-1, UBUNTU-CVE-2024-34750, openSUSE-SU-2024:14119-1, openSUSE-SU-2024:14120-1 ## What is CVE-2024-34750? CVE-2024-34750 is a high-severity denial of service vulnerability in Apache Tomcat, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Improper Handling of Exceptional Conditions, Uncontrolled Resource Consumption vulnerability in Apache Tomcat. 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. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M20, from 10.1.0-M1 through 10.1.24, from 9.0.0-M1 through 9.0.89. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0-M21, 10.1.25 or 9.0.90, which fixes the issue. Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2024-34750? 17 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, tomcat and org.apache.tomcat:tomcat-coyote. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.25 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0-M1 | 10.1.25 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.0-M21 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 11.0.0-M1 | 11.0.0-M21 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M1 | 9.0.90 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0-M1 | 9.0.90 | | `tomcat` | Bitnami | From 9.0.0 | 9.0.90, 10.1.25 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M1 | 10.1.25 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 10.1.0-M1 | 10.1.25 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.0-M21 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 11.0.0-M1 | 11.0.0-M21 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat-coyote` | Maven | From 8.5.0 to 8.5.100 | None | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0-M1 | 9.0.90 | | `org.apache.tomcat:tomcat-coyote` | Maven | From 9.0.0-M1 | 9.0.90 | | `tomcat` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-admin-webapps` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-docs-webapp` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-el-3.0-api` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-jsp-2.3-api` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-lib` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-servlet-4.0-api` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat-webapps` | AlmaLinux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-admin-webapps` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-docs-webapp` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-el-3.0-api` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-jsp-2.3-api` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-lib` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-servlet-4.0-api` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat-webapps` | AlmaLinux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat` | Rocky Linux:8 | All versions | 1:9.0.87-1.el8_10.2 | | `tomcat` | Rocky Linux:9 | All versions | 1:9.0.87-1.el9_4.2 | | `tomcat` | SUSE:Enterprise Storage 7.1 | All versions | 9.0.91-150200.68.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 9.0.91-150200.68.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 9.0.91-150200.68.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 9.0.91-150200.68.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 9.0.91-150200.68.1 | Products: Apache Tomcat, Netapp Ontap Tools. ## How do I fix CVE-2024-34750? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.25, 11.0.0-M21 or 9.0.90. ## Is CVE-2024-34750 being exploited? There is no known exploitation of CVE-2024-34750 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-34750 and fix it if it is affected. What it is: CVE-2024-34750 is a high-severity denial of service vulnerability in Apache Tomcat, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-34750 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.25 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0-M1; fixed in 10.1.25 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.0-M21 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 11.0.0-M1; fixed in 11.0.0-M21 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0 up to 8.5.100; no fix listed - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M1; fixed in 9.0.90 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0-M1; fixed in 9.0.90 - tomcat (Bitnami): affected from 9.0.0; fixed in 9.0.90, 10.1.25 - org.apache.tomcat:tomcat-coyote (Maven): affected from 10.1.0-M1; fixed in 10.1.25 - org.apache.tomcat:tomcat-coyote (Maven): affected from 10.1.0-M1; fixed in 10.1.25 - org.apache.tomcat:tomcat-coyote (Maven): affected from 11.0.0-M1; fixed in 11.0.0-M21 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-34750/ (Markdown: https://insights.sbomify.com/CVE-2024-34750/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34750 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34750 - OSV: https://osv.dev/vulnerability/CVE-2024-34750 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-34750/ Summaries are generated and may contain mistakes; the official description above is the record.