CVE-2019-0199

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 72.9%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 42 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS: 73%CVSS: 7.5Exploit: NoneExposed: 42

A fix is available — apply it.

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.

Live · internet exposure

42 internet-exposed hosts are running an affected version of CVE-2019-0199 right now.

across 15 countries (United States, China, Singapore, Korea, Republic of, Germany)top: tomcat
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.4%
KEV
Not listed

Published

April 10, 2019

Last Modified

November 21, 2024

References (70)

Vendor Advisories for CVE-2019-0199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhattomcat2020-06-04redhat
redhatpatch2019-11-20redhat
redhatjws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el8jws2019-11-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat.embed:tomcat-embed-core8.0.1 ... 8.5.9 (70 versions)8.5.38—
org.apache.tomcat:tomcat-coyote8.0.1 ... 8.5.9 (70 versions)8.5.38—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:18 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-20 18:02 UTCOSV refresh
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 02:26 UTCEPSS rescore
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:55 UTCEPSS rescore
  11. 2026-07-13 22:27 UTCEPSS rescore
  12. 2026-07-13 06:10 UTCEPSS rescore
  13. 2026-07-09 19:06 UTCEPSS rescore
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-04 06:28 UTCEPSS rescore
  16. 2026-07-04 06:28 UTCEPSS rescore
  17. 2026-07-03 13:26 UTCOSV refresh
  18. 2026-07-01 15:03 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-06-29 14:03 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-28 04:53 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 37 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-18 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-15 17:45 UTCEPSS rescore
  10. 2026-06-15 03:43 UTCOSV refresh
  11. 2026-06-12 23:09 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-11 13:57 UTCEPSS rescore
  14. 2026-06-10 22:16 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-04 13:10 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-01 13:50 UTCEPSS rescore
  26. 2026-05-31 22:29 UTCEPSS rescore
  27. 2026-05-31 22:29 UTCEPSS rescore
  28. 2026-05-29 13:41 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-27 20:42 UTCEG score recompute
  32. 2026-05-27 20:42 UTCVendor advisory
  33. 2026-05-27 13:38 UTCEPSS rescore
  34. 2026-05-26 13:42 UTCEPSS rescore
  35. 2026-05-26 13:42 UTCEPSS rescore
  36. 2026-05-26 07:17 UTCEPSS rescore
  37. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-0199?
CVE-2019-0199 is a high vulnerability published on April 10, 2019. 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…
When was CVE-2019-0199 disclosed?
CVE-2019-0199 was first published in the National Vulnerability Database on April 10, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0199 actively exploited?
CVE-2019-0199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-0199?
CVE-2019-0199 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-0199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-0199

Explore →

Is Your Infrastructure Affected by CVE-2019-0199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs