CVE-2019-9513

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.5; sources differ by 0.0.

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

A fix is available — apply it.

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

Live · internet exposure

106 internet-exposed hosts are running an affected version of CVE-2019-9513 right now.

across 27 countries (Japan, United States, China, Hong Kong, Singapore)top: nginx
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)
EG Risk
—
EPSS
99.6%
KEV
Not listed

Published

August 13, 2019

Last Modified

January 14, 2025

References (84)

Vendor Advisories for CVE-2019-9513(2)

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

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunghttp2-server (1.40.0-1ubuntu0.3) @ focal2026-05-27ubuntu
ubuntunginx-light (1.10.3-0ubuntu0.16.04.4) @ xenial2026-05-27ubuntu
redhatundertow2020-03-26redhat
redhatjbcs-httpd24-openssl-1:1.1.1-25.jbcs.el72019-11-20redhat
redhatpatch2019-11-20redhat
redhatjbcs-httpd24-openssl-1:1.1.1-25.jbcs.el62019-11-20redhat
redhatservicemesh-proxy-0:1.0.1-7.el82019-10-14redhat
redhatquay3/clair-jwt:v2.0.9-72019-10-03redhat
redhatrh-nodejs8-nodejs-0:8.16.1-2.el72019-10-02redhat
redhatjbcs-httpd24-nghttp2-0:1.39.2-1.jbcs.el72019-10-01redhat
redhatrh-nodejs10-nodejs-0:10.16.3-3.el72019-10-01redhat
redhathttpd24-nghttp2-0:1.7.1-7.el7.12019-10-01redhat
redhatnodejs:10-8000020190911085529.f8e95b4e2019-09-30redhat
redhatnginx:1.14-8000020190830002848.f8e95b4e2019-09-19redhat
redhatrh-nginx114-nginx-1:1.14.1-1.el7.12019-09-17redhat
redhatrh-nginx110-nginx-1:1.10.2-9.el7.12019-09-13redhat
redhatrh-nginx112-nginx-1:1.12.1-3.el7.12019-09-13redhat
redhatnghttp2-0:1.33.0-1.el8_0.12019-09-09redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 18× 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:30 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-20 17:04 UTCEPSS rescore
  4. 2026-07-20 09:32 UTCOSV refresh
  5. 2026-07-15 16:55 UTCEPSS rescore
  6. 2026-07-12 05:44 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-09 19:06 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-03 04:35 UTCOSV refresh
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-29 14:03 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-17 17:50 UTCEPSS rescore
  24. 2026-06-15 17:46 UTCEPSS rescore
  25. 2026-06-14 23:15 UTCEPSS rescore
Show 38 more
  1. 2026-06-14 23:15 UTCEPSS rescore
  2. 2026-06-14 20:43 UTCOSV refresh
  3. 2026-06-13 22:58 UTCEPSS rescore
  4. 2026-06-12 23:09 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-11 13:58 UTCEPSS rescore
  7. 2026-06-10 22:16 UTCEPSS rescore
  8. 2026-06-10 22:16 UTCEPSS rescore
  9. 2026-06-10 13:19 UTCEPSS rescore
  10. 2026-06-08 14:15 UTCEPSS rescore
  11. 2026-06-08 14:15 UTCEPSS rescore
  12. 2026-06-08 14:15 UTCEPSS rescore
  13. 2026-06-07 15:23 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-05 22:45 UTCEPSS rescore
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-04 13:10 UTCEPSS rescore
  20. 2026-06-04 13:10 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-02 20:11 UTCEPSS rescore
  23. 2026-06-01 13:50 UTCEPSS rescore
  24. 2026-06-01 13:50 UTCEPSS rescore
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-31 22:29 UTCEPSS rescore
  27. 2026-05-31 00:14 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-29 13:42 UTCEPSS rescore
  30. 2026-05-28 13:43 UTCEPSS rescore
  31. 2026-05-28 13:43 UTCEPSS rescore
  32. 2026-05-27 16:01 UTCEG score recompute
  33. 2026-05-27 16:01 UTCVendor advisory
  34. 2026-05-27 16:01 UTCGHSA enrichment
  35. 2026-05-27 13:39 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-26 13:42 UTCEPSS rescore
  38. 2026-05-24 16:47 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-9513?
CVE-2019-9513 is a high vulnerability published on August 13, 2019. Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.
When was CVE-2019-9513 disclosed?
CVE-2019-9513 was first published in the National Vulnerability Database on August 13, 2019, with the most recent update on January 14, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-9513 actively exploited?
CVE-2019-9513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-9513?
CVE-2019-9513 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-9513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9513, 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

Explore the affected products and dependency analysis for CVE-2019-9513

Explore →

Is Your Infrastructure Affected by CVE-2019-9513?

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

Start Free Scan →Browse All CVEs