CVE-2019-5737

In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.

Published: 2019-03-28 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-5737 is rated Moderate Risk (58.8/100): CVSS High severity, with high exploitation likelihood (EPSS 16.18%, 97th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-5737

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 26.35% 16.18% -10.17%
2 2026-03-08 36.45% 26.35% -10.10%
3 2026-01-11 — 36.45% —

Full EPSS history (25 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-5737

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-5737

OS Trackers for CVE-2019-5737

vendor priority summary link
alpine — CVE-2019-5737: 2 source package rows (nodejs, nodejs-current); 52 state rows across 17 repos (3.10-main, 3.11-main, 3.12-main, 3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, 3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 17, open 35. https://security.alpinelinux.org/vuln/CVE-2019-5737
debian unimportant CVE-2019-5737 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-5737
gentoo normal CVE-2019-5737: 1 GLSA(s) (202003-48), 1 atom(s) (net-libs/nodejs); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-5737
redhat low — https://access.redhat.com/security/cve/CVE-2019-5737
suse medium CVE-2019-5737 severity moderate: SUSE including 75 source package names (MozillaFirefox-68.2.0-78.51.4, MozillaFirefox-branding-SLED-68-21.9.8, …), 209 product×package rows across 17 product lines (SUSE Enterprise Storage 4, SUSE Liberty Linux 8, … (17 product lines)): Fixed 209. https://www.suse.com/security/cve/CVE-2019-5737/
ubuntu medium CVE-2019-5737 medium priority: Ubuntu including 1 source packages (nodejs), 19 status rows across 19 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 14, released 3, ignored 1, needed 1. https://ubuntu.com/security/CVE-2019-5737

Affected software / configurations for CVE-2019-5737

Vendor Product Version Raw CPE
nodejs node.js >= 6.0.0, < 6.17.0 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
nodejs node.js >= 8.0.0, < 8.15.1 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
nodejs node.js >= 10.0.0, < 10.15.2 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
nodejs node.js >= 11.0.0, < 11.10.1 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
opensuse leap 42.3 cpe:2.3:o:opensuse:leap:42.3:*:*:*:*:*:*:*

References for CVE-2019-5737

cvelogic Threat Intelligence