CVE-2019-9515

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 88%
CISA-KEV: Not listedEPSS PROB: 88%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
80(Track)
EG Risk 80/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
Severity90% × 45%
Exploitation88% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
88%
EPSS %ILE
100%
KEV
Not listed

Published

August 13, 2019

Last Modified

January 14, 2025

References (76)

Vendor Advisories for CVE-2019-9515(6)

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

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibnetty-java (1:4.1.7-4ubuntu0.1+esm1) @ bionic2026-05-27ubuntu
ubuntutwisted-doc (18.9.0-3ubuntu1.1) @ eoan2026-05-27ubuntu
redhateap7-wildfly-elytron-0:1.1.13-1.Final_redhat_00001.1.ep7.el72024-08-26redhat
redhatnetty2020-07-29redhat
redhatundertow2020-06-15redhat
redhatpatch2020-05-18redhat
redhatpatch2020-04-14redhat
redhatpatch2020-03-23redhat
redhatrh-sso7-keycloak-0:4.8.15-1.Final_redhat_00001.1.el8sso2019-12-02redhat
redhatrh-sso7-keycloak-0:4.8.15-1.Final_redhat_00001.1.el6sso2019-12-02redhat
redhatrh-sso7-keycloak-0:4.8.15-1.Final_redhat_00001.1.el7sso2019-12-02redhat
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
redhateap7-yasson-0:1.0.5-1.redhat_00001.1.el7eap2019-11-26redhat
redhatundertow-core2019-11-26redhat
redhatrh-nodejs8-nodejs-0:8.16.1-2.el72019-10-02redhat
redhatrh-nodejs10-nodejs-0:10.16.3-3.el72019-10-01redhat
redhatnodejs:10-8000020190911085529.f8e95b4e2019-09-30redhat
redhatopenshift4/ose-sriov-network-device-plugin:v4.1.18-2019092019152019-09-26redhat
redhatskydive-0:0.20.5-2.el7ost2019-09-19redhat
redhatopenshift4/ose-operator-registry:v4.1.15-2019090416052019-09-12redhat

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(2)

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

Additional Vendor Advisories

(19)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-9515?
CVE-2019-9515 is a critical vulnerability published on August 13, 2019. Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost…
When was CVE-2019-9515 disclosed?
CVE-2019-9515 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-9515 actively exploited?
CVE-2019-9515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2019-9515?
CVE-2019-9515 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-9515?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9515, 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-9515

Explore →

Is Your Infrastructure Affected by CVE-2019-9515?

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

Start Free Scan →Browse All CVEs