Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-15896: Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS han

63
This week
CRITICAL 9.1REMOTEWATCHLISTUPGRADE

CVE-2017-15896 is a critical-severity flaw (CVSS 9.1) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modules in a way that bypassed TLS authentication and encryption.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
Published2017-12-11
Last modified2026-06-17
Publisher (CNA): Node.js · Vendor: nodejs

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

nodejs node.js UPGRADE
Affected: >= 4.0.0 and <= 4.1.2 · >= 4.2.0 and < 4.8.7 · >= 6.0.0 and <= 6.8.1 · >= 6.9.0 and < 6.12.2 · >= 8.0.0 and <= 8.8.1 · >= 8.9.0 and < 8.9.3 · >= 9.0.0 and < 9.2.1
Fixed in: 4.8.7, 6.12.2, 8.9.3, 9.2.1
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to 4.8.7 (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.
3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_4.0.0> sudo apt-mark hold node.js
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add node.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2017-15896?

node.js: upgrade to 4.8.7, 6.12.2, 8.9.3, 9.2.1. Exact commands for each OS are on this page.

Is CVE-2017-15896 being exploited?

CVE-2017-15896 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-2017-15896 affect?

CVE-2017-15896 affects node.js. Severity is critical (CVSS 9.1). Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modul

How urgent is CVE-2017-15896?

Priority 63/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Node.js vulnerabilities · OpenSSL vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.