# Apache Tomcat has an Improper Input Validation vulnerability Advisory record · `GHSA-mgp5-rv84-w37q` - **Identifiers:** `GHSA-mgp5-rv84-w37q` · `BIT-tomcat-2026-24734` · `CVE-2026-24734` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-295](https://cwe.mitre.org/data/definitions/295.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) - **Published:** 17 Feb 2026 - **Updated:** 4 Nov 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 17 Feb 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=11.0.0-M1, <11.0.18 || >=10.1.0-M7, <10.1.52 || >=9.0.83, <9.0.115`; fixed in `11.0.18`, `10.1.52`, `9.0.115` - `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=11.0.0-M1, <11.0.18 || >=10.1.0-M7, <10.1.52 || >=9.0.83, <9.0.115`; fixed in `11.0.18`, `10.1.52`, `9.0.115` - `org.apache.tomcat:tomcat-coyote-ffm` (Maven): affected `>=11.0.0-M1, <11.0.18 || >=10.1.0-M7, <10.1.52 || >=9.0.83, <9.0.115`; fixed in `11.0.18`, `10.1.52`, `9.0.115` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Tomcat versions 9.0.83 to 9.0.114, 10.1.0-M7 to 10.1.51, and 11.0.0-M1 to 11.0.17 (tomcat-coyote and tomcat-embed-core) are affected. When an OCSP responder is used, incomplete verification and freshness checks can let certificate revocation be bypassed. Upgrade to 11.0.18, 10.1.52, or 9.0.115 or later. 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:H/A:N`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0057, the 47th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 17 Feb 2026, 21:31 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-mgp5-rv84-w37q) - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mgp5-rv84-w37q) ## Sources - [GitHub Advisory Database: GHSA-mgp5-rv84-w37q](https://github.com/advisories/GHSA-mgp5-rv84-w37q) - [OSV: GHSA-mgp5-rv84-w37q](https://osv.dev/vulnerability/GHSA-mgp5-rv84-w37q) - - - - - - - - - - - - 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: .