# Apache Tomcat Request and/or response mix-up Advisory record · `GHSA-qvf5-hvjx-wm27` - **Identifiers:** `GHSA-qvf5-hvjx-wm27` · `BIT-tomcat-2024-52317` · `CVE-2024-52317` - **State:** Confirmed - **Severity:** CVSS 6.5 Medium - **Critical:** No - **Weakness (CWE):** [CWE-326](https://cwe.mitre.org/data/definitions/326.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 18 Nov 2024 - **Updated:** 24 Jan 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 18 Nov 2024, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=9.0.92, <9.0.96 || >=10.1.27, <10.1.31 || >=11.0.0-M23, <11.0.0`; fixed in `9.0.96`, `10.1.31`, `11.0.0` - `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=9.0.92, <9.0.96 || >=10.1.27, <10.1.31 || >=11.0.0-M23, <11.0.0`; fixed in `9.0.96`, `10.1.31`, `11.0.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Tomcat versions 9.0.92 through 9.0.95, 10.1.27 through 10.1.30, and 11.0.0-M23 through 11.0.0-M26 are affected, as are the tomcat-embed-core and tomcat-coyote packages in those ranges. Incorrect recycling of request and response objects used for HTTP/2 requests can cause responses or requests to be mixed up between users. The source does not state what access an attacker needs. Upgrade to 9.0.96, 10.1.31, or 11.0.0, which fix the issue. Written 7 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 - 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.021, the 81st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 15:11 UTC: First seen by agentprime - 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qvf5-hvjx-wm27) ## Sources - [GitHub Advisory Database: GHSA-qvf5-hvjx-wm27](https://github.com/advisories/GHSA-qvf5-hvjx-wm27) - [OSV: GHSA-qvf5-hvjx-wm27](https://osv.dev/vulnerability/GHSA-qvf5-hvjx-wm27) - - - - - - - - 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: .