Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-7160: The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to pe

55
This week
HIGH 8.8UPGRADE

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

The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP conn

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance9.5% (top 5%)
CISA exploited listNo
WeaknessCWE-350, CWE-290
Published2018-05-17
Last modified2026-10-08
Publisher (CNA): Node.js · Vendor: nodejs

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

nodejs node.js UPGRADE
Affected: >= 6.0.0 and <= 6.8.1 · >= 6.9.0 and < 6.14.0 · >= 8.0.0 and <= 8.8.1 · >= 8.9.0 and < 8.11.0 · >= 9.0.0 and < 9.10.0
Fixed in: 6.14.0, 8.11.0, 9.10.0
Safe to downgrade to: a release before 6.0.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to 6.14.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.
3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_6.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_6.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-2018-7160?

node.js: upgrade to 6.14.0, 8.11.0, 9.10.0. Exact commands for each OS are on this page.

Is CVE-2018-7160 being exploited?

CVE-2018-7160 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-2018-7160 affect?

CVE-2018-7160 affects node.js. Severity is high (CVSS 8.8). The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another

How urgent is CVE-2018-7160?

Priority 55/100. High severity; EPSS top 5%: very likely to be exploited

Software pages

Node.js 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.