CVE-2019-9512

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 51.2%, top 2% 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
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

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

Published

August 13, 2019

Last Modified

November 21, 2024

References (130)

Vendor Advisories for CVE-2019-9512(6)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatcontainernetworking-plugins-0:0.8.1-4.el7_72020-02-04redhat
redhatcontainer-tools:rhel8-8010020191126140055.c294d1612019-12-17redhat
redhatcontainer-tools:1.0-8010020191126173920.c294d1612019-12-17redhat
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
redhatrh-sso7-keycloak-0:4.8.15-1.Final_redhat_00001.1.el8sso2019-12-02redhat
redhateap7-yasson-0:1.0.5-1.redhat_00001.1.el7eap2019-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.el6eap2019-11-26redhat
redhatundertow-core2019-11-26redhat
redhatopenshift-external-storage-0:0.0.2-9.gitd3c94f0.el72019-11-18redhat
redhatopenshift-eventrouter-0:0.2-3.gited73fb6.el72019-10-30redhat
redhatgolang-github-prometheus-promu-0:0.5.0-2.git642a960.el72019-10-29redhat
redhatopenvswitch-ovn-kubernetes-0:0.1.0-3.el72019-10-24redhat
redhatopenshift-monitor-project-lifecycle-0:3.11.51-2.git.59.7b59e29.el72019-10-18redhat
redhatpivot-0:0.0.5-2.el82019-10-16redhat
redhatquay3/clair-jwt:v2.0.9-72019-10-03redhat
redhatrh-nodejs8-nodejs-0:8.16.1-2.el72019-10-02redhat

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)
Go(2)
PackageVulnerable rangeFixed inDependents
golang.org/x/net—0.0.0-20190813141303-74dc4d7220e7—
stdlib—1.12.8—

Weakness Classification(1)

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

Additional Vendor Advisories

(23)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-9512?
CVE-2019-9512 is a high vulnerability published on August 13, 2019. Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU,…
When was CVE-2019-9512 disclosed?
CVE-2019-9512 was first published in the National Vulnerability Database on August 13, 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-9512 actively exploited?
CVE-2019-9512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-9512?
CVE-2019-9512 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-9512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9512, 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-9512

Explore →

Is Your Infrastructure Affected by CVE-2019-9512?

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

Start Free Scan →Browse All CVEs