# Apache Tomcat Denial of Service due to improper input validation vulnerability for HTTP/2 requests Advisory record · `GHSA-7w75-32cg-r6g2` - **Identifiers:** `GHSA-7w75-32cg-r6g2` · `BIT-tomcat-2024-24549` · `CVE-2024-24549` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** Yes: CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) - **Published:** 13 Mar 2024 - **Updated:** 13 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 13 Mar 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 7.5 (7.0 or more) and EPSS 0.23 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=11.0.0-M1, <11.0.0-M17 || >=10.1.0-M1, <10.1.19 || >=9.0.0-M1, <9.0.86 || >=8.5.0, <8.5.99`; fixed in `11.0.0-M17`, `10.1.19`, `9.0.86`, `8.5.99` - `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=8.5.0, <8.5.99 || >=9.0.0-M1, <9.0.86 || >=10.1.0-M1, <10.1.19 || >=11.0.0-M1, <11.0.0-M17`; fixed in `8.5.99`, `9.0.86`, `10.1.19`, `11.0.0-M17` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Tomcat (tomcat-coyote and tomcat-embed-core packages) versions 8.5.0 through 8.5.98, 9.0.0-M1 through 9.0.85, 10.1.0-M1 through 10.1.18, and 11.0.0-M1 through 11.0.0-M16 are affected. A remote client sending HTTP/2 requests whose headers exceed configured limits can cause denial of service, because the stream is not reset until all headers are processed. Upgrade to 8.5.99, 9.0.86, 10.1.19, 11.0.0-M17, or later in the affected line. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.23, the 97th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7w75-32cg-r6g2) ## Sources - [GitHub Advisory Database: GHSA-7w75-32cg-r6g2](https://github.com/advisories/GHSA-7w75-32cg-r6g2) - [OSV: GHSA-7w75-32cg-r6g2](https://osv.dev/vulnerability/GHSA-7w75-32cg-r6g2) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .