# Apache Tomcat - HTTP/2 request headers not validated Advisory record · `GHSA-r29c-68gh-xp6x` - **Identifiers:** `GHSA-r29c-68gh-xp6x` · `BIT-tomcat-2026-41293` · `CVE-2026-41293` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) - **Published:** 12 May 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 12 May 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.8: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=8.5.0, <9.0.118 || >=10.1.0-M1, <10.1.55 || >=11.0.0-M1, <11.0.22`; fixed in `9.0.118`, `10.1.55`, `11.0.22` - `org.apache.tomcat:tomcat` (Maven): affected `>=8.5.0, <9.0.118 || >=10.1.0-M1, <10.1.55 || >=11.0.0-M1, <11.0.22`; fixed in `9.0.118`, `10.1.55`, `11.0.22` - `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=8.5.0, <9.0.118 || >=10.1.0-M1, <10.1.55 || >=11.0.0-M1, <11.0.22`; fixed in `9.0.118`, `10.1.55`, `11.0.22` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Tomcat (tomcat-embed-core, tomcat, and tomcat-coyote Maven packages) versions 8.5.0 up to but not including 9.0.118, 10.1.0-M1 up to but not including 10.1.55, and 11.0.0-M1 up to but not including 11.0.22 do not validate HTTP/2 request headers. The source gives few details on the exact impact: an application that assumes header values exposed through the Servlet API are specification compliant may behave unexpectedly. Upgrade to 9.0.118, 10.1.55, 11.0.22, or a later release in the same 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 - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.017, the 77th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r29c-68gh-xp6x) ## Sources - [GitHub Advisory Database: GHSA-r29c-68gh-xp6x](https://github.com/advisories/GHSA-r29c-68gh-xp6x) - [OSV: GHSA-r29c-68gh-xp6x](https://osv.dev/vulnerability/GHSA-r29c-68gh-xp6x) - - - - - - - - - - - - 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: .