# Apache Tomcat Denial of Service vulnerability

Advisory record · `GHSA-qcxh-w3j9-58qr`

- **Identifiers:** `GHSA-qcxh-w3j9-58qr` · `CVE-2019-0199`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 15 Jun 2020
- **Updated:** 20 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Jun 2020, 18:51 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.73 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=9.0.0, <9.0.16 || >=8.0.0, <8.5.38`; fixed in `9.0.16`, `8.5.38`
- `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=9.0.0, <9.0.16 || >=8.0.0, <8.5.38`; fixed in `9.0.16`, `8.5.38`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Tomcat's tomcat-embed-core and tomcat-coyote packages are affected in versions 9.0.0 to before 9.0.16 and 8.0.0 to before 8.5.38. A remote client that can connect over HTTP/2 can send excessive SETTINGS frames and hold streams open without reading or writing data, which can block server threads used for blocking I/O and exhaust them. Upgrade to 9.0.16 or 8.5.38. No workaround is listed.

Written 3 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.0: `CVSS:3.0/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.73, the 99th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qcxh-w3j9-58qr)

## Sources

- [GitHub Advisory Database: GHSA-qcxh-w3j9-58qr](https://github.com/advisories/GHSA-qcxh-w3j9-58qr)
- [OSV: GHSA-qcxh-w3j9-58qr](https://osv.dev/vulnerability/GHSA-qcxh-w3j9-58qr)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-0199>
- <https://lists.apache.org/thread.html/e1b0b273b6e8ddcc72c9023bc2394b1276fc72664144bf21d0a87995@%3Cannounce.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/e56886e1bac9319ecce81b3612dd7a1a43174a3a741a1c805e16880e%40%3Ccommits.tomee.apache.org%3E>
- <https://lists.apache.org/thread.html/e56886e1bac9319ecce81b3612dd7a1a43174a3a741a1c805e16880e@%3Ccommits.tomee.apache.org%3E>
- <https://lists.apache.org/thread.html/e85e83e9954f169bbb77b44baae5a33d8de878df557bb32b7f793661%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/e85e83e9954f169bbb77b44baae5a33d8de878df557bb32b7f793661@%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/e87733036e8c84ea648cdcdca3098f3c8a897e2652c33062b2b1535c%40%3Cusers.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/e87733036e8c84ea648cdcdca3098f3c8a897e2652c33062b2b1535c@%3Cusers.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d@%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0@%3Cdev.tomcat.apache.org%3E>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qcxh-w3j9-58qr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qcxh-w3j9-58qr/>. Everything for agents: <https://agentprime.io/llms.txt>.
