Vulnerability · CVE-2019-0199
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients…
Published Apr 10, 2019 · catalog updated Jun 17, 2026 · the affected product
Last checked Nov 9, 2026. A connected source was read within the last 7 days.
Check this week
CVE-2019-0199 is not in CISA KEV. FIRST estimates a 72.86% chance of exploitation in the next 30 days. Check whether you run the affected product.
Gaps on this record
- No plain product name is stored. The page cannot tell you which product to check.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-73180 · Medium
- CVE-2026-68763 · High
- CVE-2026-68569 · High
- CVE-2026-68525 · Critical
- CVE-2026-66422 · High
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 72.86%
- Remediation
- Version ranges on file
- Affected products
- cpe apache/tomcat
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe apache/tomcat9.0.0
- cpe apache/tomcat>= 8.5.0, <= 8.5.37
- cpe apache/tomcat>= 9.0.1, <= 9.0.14
How to fix CVE-2019-0199
Upgrade
CVE-2019-0199 lists a fix boundary at 8.5.37. Compare the installed build with that boundary before you change production.
Version check
Affected <= 8.5.37
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2019-0199 is not in CISA KEV. FIRST estimates a 72.86% chance of exploitation in the next 30 days. Check whether you run the affected product.
Which versions are affected?
Compare what you have installed with 9.0.0, >= 8.5.0, <= 8.5.37, >= 9.0.1, <= 9.0.14. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-400: Uncontrolled Resource Consumption. EPSS 72.86%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Apr 10, 2019 · Monitored products — critical
Detected
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thr
Jun 17, 2026 · Monitored products — critical
Updated
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thr
Sources
- CVE.orgVulnerability recordCVE-2019-0199
Official CVE identifier
cve.org - Monitored products — criticalVendor advisoryCVE-2019-0199
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thr
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 9, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 4, 2026
- Monitored products — criticalNov 3, 2026