Skip to main content
No exploitation reportedFix available

CVE-2019-9512

No exploitation reported by the sources we read.

  • Published2019-08-13
  • Fixed in12.8.1 · 10.16.3 · 8.16.1
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2019-08-1321:15CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-9512?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-9512?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Node.js
BranchAffectedFixed in
12.x≥ 12.0.0, < 12.8.112.8.1
10.x≥ 10.13.0, < 10.16.310.16.3
8.x≥ 8.9.0, < 8.16.18.16.1
8.x≥ 8.0.0, ≤ 8.8.1no fix published
10.x≥ 10.0.0, ≤ 10.12.0no fix published
Apache traffic server
BranchAffectedFixed in
6.x≥ 6.0.0, ≤ 6.2.3no fix published
7.x≥ 7.0.0, ≤ 7.1.6no fix published
8.0≥ 8.0.0, ≤ 8.0.3no fix published
Apple swiftnioversion to verify
BranchAffectedFixed in
1.x≥ 1.0.0, ≤ 1.4.0no fix published

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Node.js to 12.8.1 · 10.16.3 · 8.16.1

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • CNACVSS 3.07.5read 2026-10-23
  • NVDCVSS 2.07.8read 2026-10-23
  • CNAweakness (CWE)CWE-400read 2026-10-23
  • NVDweakness (CWE)CWE-400read 2026-10-23
  • FIRST EPSSEPSS score83.4 %read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2019-08-13
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2019-9512?

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.

Is CVE-2019-9512 actively exploited?

Active exploitation of CVE-2019-9512 has not been confirmed. Its EPSS score was 83.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-9512?

CVE-2019-9512 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month