CVE-2019-5739: Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and e

Q: How do I fix CVE-2019-5739?

node.js: upgrade to newer than 6.16.0; leap: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2019-5739 being exploited?

CVE-2019-5739 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-5739 affect?

CVE-2019-5739 affects node.js, leap. Severity is high (CVSS 7.5). Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 a

Q: How urgent is CVE-2019-5739?

Priority 54/100. High severity; EPSS top 8%: very likely to be exploited; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADEMITIGATE

CVE-2019-5739 is a high-severity flaw (CVSS 7.5) affecting node.js, leap. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 and earlier is a potential Denial of Service (DoS) attack vector. Node.js 6.17.0 introduces server.keepAliveTimeout and the 5-second default.

Why this priority

High severity
EPSS top 8%: very likely to be exploited
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	4.9% (top 8%)
CISA exploited list	No
Weakness	CWE-400, CWE-770
Published	2019-03-28
Last modified	2026-06-17

Publisher (CNA): Node.js · Vendor: nodejs · opensuse

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-03-28 17:29 UTCPublished CVE record published
2026-06-17 02:38 UTCUpdated Record last modified

nodejs node.js UPGRADE

Affected: <= 6.16.0

Fixed in: newer than 6.16.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy node.js || rpm -q node.js || node.js --version

2. UPGRADE to newer than 6.16.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade node.js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade node.js

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

opensuse leap MITIGATE

Affected: 42.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 42.3

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-5739?

node.js: upgrade to newer than 6.16.0; leap: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-5739 being exploited?

CVE-2019-5739 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-5739 affect?

CVE-2019-5739 affects node.js, leap. Severity is high (CVSS 7.5). Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 a

How urgent is CVE-2019-5739?

Priority 54/100. High severity; EPSS top 8%: very likely to be exploited; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2026-111497 CRITICAL 9.8 EXPLOITED UPGRADE UPGRADE Google Brotli Unchecked Return Value Vulnerability
CVE-2026-48617 HIGH 8.2 UPGRADE A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalida
CVE-2026-48937 HIGH 7.5 UPGRADE A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` fra
CVE-2026-48931 LOW 3.7 DOWNGRADE A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client h
CVE-2026-48933 HIGH 7.5 DOWNGRADE A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multi

References

← Back to latest CVEs