CVE-2019-9511

HIGHNVD 7.58.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 60% probability of exploitation within the next 30 days (top 1.0% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 245 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 60%
CISA-KEV: Not listedEPSS PROB: 60%CVSS: 7.5Exploit: Elevated riskExposed: 245

A fix is available — apply it.

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

Live · internet exposure

245 internet-exposed hosts are running an affected version of CVE-2019-9511 right now.

across 36 countries (United States, Japan, China, Hong Kong, France)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
8.3(high)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation60% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
60%
EPSS %ILE
99%
KEV
Not listed

Published

August 13, 2019

Last Modified

January 14, 2025

References (94)

Vendor Advisories for CVE-2019-9511(15)

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

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunghttp2-server (1.7.1-1ubuntu0.1~esm2) @ xenial2026-05-27ubuntu
ubuntunginx-light (1.10.3-0ubuntu0.16.04.4) @ xenial2026-05-27ubuntu
redhateap7-wildfly-elytron-0:1.1.13-1.Final_redhat_00001.1.ep7.el72024-08-26redhat
redhatundertow2020-07-28redhat
redhatpatch2020-05-18redhat
redhatpatch2020-04-14redhat
redhatpatch2020-03-23redhat
redhateap7-yasson-0:1.0.5-1.redhat_00001.1.el6eap2019-11-26redhat
redhateap7-yasson-0:1.0.5-1.redhat_00001.1.el8eap2019-11-26redhat
redhatundertow-core2019-11-26redhat
redhateap7-yasson-0:1.0.5-1.redhat_00001.1.el7eap2019-11-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
redhatrh-nodejs10-nodejs-0:10.16.3-3.el72019-10-01redhat
redhatjbcs-httpd24-nghttp2-0:1.39.2-1.jbcs.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-nginx112-nginx-1:1.12.1-3.el7.12019-09-13redhat
redhatrh-nginx110-nginx-1:1.10.2-9.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.

Affected Packages

(50 across 24 ecosystems)
Alpine:v3.15(3)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
nodejs—10.16.3-r0—
Alpine:v3.24(3)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
nodejs—10.16.3-r0—
Alpine:v3.9(3)
PackageVulnerable rangeFixed inDependents
nghttp2—1.35.1-r1—
nginx—1.14.1-r2—
nodejs—10.16.3-r0—
Alpine:v3.10(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.11(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.12(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.13(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.14(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.16(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.17(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.18(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.19(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.20(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.16.1-r0—
Alpine:v3.8(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—
nginx—1.14.1-r1—
Debian:10(2)
PackageVulnerable rangeFixed inDependents
nghttp21.36.0-21.36.0-2+deb10u1—
nginx1.14.2-21.14.2-2+deb10u1—
Debian:11(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-1—
nginx—1.14.2-3—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-1—
nginx—1.14.2-3—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-1—
nginx—1.14.2-3—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-1—
nginx—1.14.2-3—
Debian:9(2)
PackageVulnerable rangeFixed inDependents
nghttp21.18.1-11.18.1-1+deb9u1—
nginx1.10.3-1, 1.10.3-1+deb9u1, 1.10.3-1+deb9u1~bpo8+1, 1.10.3-1+deb9u1~bpo8+2, 1.10.3-1+deb9u21.10.3-1+deb9u3—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
nghttp2—1.39.2-r0—

Weakness Classification(2)

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

Additional Vendor Advisories

(11)

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 6× in last 7d / 17× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-09-08 06:22 UTCOSV refresh
  2. 2026-09-07 15:57 UTCEPSS rescore
  3. 2026-09-06 13:44 UTCEPSS rescore
  4. 2026-09-05 15:24 UTCEPSS rescore
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-02 14:08 UTCEPSS rescore
  7. 2026-08-30 01:18 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:42 UTCEPSS rescore
  10. 2026-08-25 13:45 UTCEPSS rescore
  11. 2026-08-21 16:44 UTCOSV refresh
  12. 2026-08-19 17:00 UTCEPSS rescore
  13. 2026-08-18 13:44 UTCEPSS rescore
  14. 2026-08-17 13:43 UTCEPSS rescore
  15. 2026-08-15 01:26 UTCEPSS rescore
  16. 2026-08-13 21:57 UTCEPSS rescore
  17. 2026-08-12 13:47 UTCEPSS rescore
  18. 2026-08-07 16:23 UTCEPSS rescore
  19. 2026-08-06 01:54 UTCOSV refresh
  20. 2026-08-05 19:13 UTCEPSS rescore
  21. 2026-08-04 15:05 UTCEPSS rescore
  22. 2026-08-04 10:34 UTCEPSS rescore
  23. 2026-07-30 01:27 UTCEPSS rescore
  24. 2026-07-28 15:32 UTCEPSS rescore
  25. 2026-07-26 14:51 UTCEPSS rescore
Show 75 more
  1. 2026-07-25 14:14 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-23 14:15 UTCEPSS rescore
  4. 2026-07-23 01:47 UTCEG score recompute▲ 0.80
  5. 2026-07-22 22:30 UTCEG score recompute
  6. 2026-07-22 14:05 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-21 15:22 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-20 09:32 UTCOSV refresh
  11. 2026-07-19 14:28 UTCEPSS rescore
  12. 2026-07-19 14:28 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-19 02:26 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-15 16:55 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-13 22:27 UTCEPSS rescore
  20. 2026-07-13 06:10 UTCEPSS rescore
  21. 2026-07-13 06:10 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-12 05:43 UTCEPSS rescore
  24. 2026-07-11 08:24 UTCEPSS rescore
  25. 2026-07-11 08:24 UTCEPSS rescore
  26. 2026-07-09 19:06 UTCEPSS rescore
  27. 2026-07-07 13:43 UTCEPSS rescore
  28. 2026-07-05 02:27 UTCEPSS rescore
  29. 2026-07-03 04:35 UTCOSV refresh
  30. 2026-07-01 15:03 UTCEPSS rescore
  31. 2026-07-01 15:03 UTCEPSS rescore
  32. 2026-06-28 04:54 UTCEPSS rescore
  33. 2026-06-28 04:54 UTCEPSS rescore
  34. 2026-06-27 03:06 UTCEPSS rescore
  35. 2026-06-25 13:47 UTCEPSS rescore
  36. 2026-06-25 13:47 UTCEPSS rescore
  37. 2026-06-23 21:31 UTCEPSS rescore
  38. 2026-06-23 21:31 UTCEPSS rescore
  39. 2026-06-21 01:57 UTCEPSS rescore
  40. 2026-06-21 01:57 UTCEPSS rescore
  41. 2026-06-18 17:50 UTCEPSS rescore
  42. 2026-06-18 17:50 UTCEPSS rescore
  43. 2026-06-17 17:50 UTCEPSS rescore
  44. 2026-06-16 17:50 UTCEPSS rescore
  45. 2026-06-15 17:46 UTCEPSS rescore
  46. 2026-06-14 23:15 UTCEPSS rescore
  47. 2026-06-14 23:15 UTCEPSS rescore
  48. 2026-06-14 20:43 UTCOSV refresh
  49. 2026-06-13 22:58 UTCEPSS rescore
  50. 2026-06-12 23:09 UTCEPSS rescore
  51. 2026-06-12 23:09 UTCEPSS rescore
  52. 2026-06-11 13:58 UTCEPSS rescore
  53. 2026-06-10 22:16 UTCEPSS rescore
  54. 2026-06-10 22:16 UTCEPSS rescore
  55. 2026-06-10 13:19 UTCEPSS rescore
  56. 2026-06-08 14:15 UTCEPSS rescore
  57. 2026-06-08 14:15 UTCEPSS rescore
  58. 2026-06-08 14:15 UTCEPSS rescore
  59. 2026-06-07 15:23 UTCEPSS rescore
  60. 2026-06-07 15:23 UTCEPSS rescore
  61. 2026-06-06 13:45 UTCEPSS rescore
  62. 2026-06-06 13:45 UTCEPSS rescore
  63. 2026-06-05 22:45 UTCEPSS rescore
  64. 2026-06-04 13:10 UTCEPSS rescore
  65. 2026-06-04 13:10 UTCEPSS rescore
  66. 2026-06-02 20:11 UTCEPSS rescore
  67. 2026-06-02 20:11 UTCEPSS rescore
  68. 2026-06-01 13:50 UTCEPSS rescore
  69. 2026-06-01 13:50 UTCEPSS rescore
  70. 2026-05-31 22:29 UTCEPSS rescore
  71. 2026-05-31 22:29 UTCEPSS rescore
  72. 2026-05-31 00:14 UTCEPSS rescore
  73. 2026-05-31 00:14 UTCEPSS rescore
  74. 2026-05-29 13:42 UTCEPSS rescore
  75. 2026-05-28 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-9511?
CVE-2019-9511 is a high vulnerability published on August 13, 2019. Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to…
When was CVE-2019-9511 disclosed?
CVE-2019-9511 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-9511 actively exploited?
CVE-2019-9511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60% probability of exploitation in the next 30 days, which ranks it in the top 0.9% of all scored CVEs.
What is the CVSS score of CVE-2019-9511?
CVE-2019-9511 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3.
How do I remediate CVE-2019-9511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9511, 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-9511

Explore →

Is Your Infrastructure Affected by CVE-2019-9511?

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

Start Free Scan →Browse All CVEs