CVE-2018-7160 [High] | RCE in Node.js

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 connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-01	1.58%	1.49%	-0.09%
2	2025-11-21	2.35%	1.58%	-0.77%
3	2025-11-18	—	2.35%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-01

1.58%

1.49%

-0.09%

2025-11-21

2.35%

1.58%

-0.77%

2025-11-18

—

2.35%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
6.8	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.6	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

6.8

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.6

6.4

[email protected]

OS Trackers for CVE-2018-7160

vendor	priority	summary	link
`alpine`	high	CVE-2018-7160: 2 source package rows (nodejs, nodejs-current); 27 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 10.	https://security.alpinelinux.org/vuln/CVE-2018-7160
`debian`	unimportant	CVE-2018-7160 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-2018-7160
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2018-7160
`suse`	medium	CVE-2018-7160 severity moderate: SUSE including 55 source package names (MozillaFirefox-68.2.0-78.51.4, MozillaFirefox-branding-SLED-68-21.9.8, …), 151 product×package rows across 7 product lines (SUSE Enterprise Storage 4, SUSE Linux Enterprise Module for Web and Scripting 12, … (7 product lines)): Fixed 149, Known Not Affected 2.	https://www.suse.com/security/cve/CVE-2018-7160/
`ubuntu`	medium	CVE-2018-7160 medium priority: Ubuntu including 1 source packages (nodejs), 15 status rows across 15 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, trusty, upstream, xenial): not-affected 12, released 2, ignored 1.	https://ubuntu.com/security/CVE-2018-7160

Affected software / configurations for CVE-2018-7160

Vendor	Product	Version	Raw CPE
nodejs	node.js	>= 6.0.0, <= 6.8.1	cpe:2.3:a:nodejs:node.js:::::-:::*
nodejs	node.js	>= 6.9.0, < 6.14.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 8.0.0, <= 8.8.1	cpe:2.3:a:nodejs:node.js:::::-:::*
nodejs	node.js	>= 8.9.0, < 8.11.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 9.0.0, < 9.10.0	cpe:2.3:a:nodejs:node.js:::::-:::*

References for CVE-2018-7160

URL	Tags
https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/	Vendor Advisory
https://support.f5.com/csp/article/K63025104?utm_source=f5support&amp%3Butm_medium=RSS
https://www.oracle.com//security-alerts/cpujul2021.html	Third Party Advisory

URL

CVE-2018-7160

Exploit prediction scoring system (EPSS) score for CVE-2018-7160

Common vulnerability scoring system (CVSS) metrics for CVE-2018-7160

Weakness enumeration for CVE-2018-7160

GitHub Security Advisory for CVE-2018-7160

OS Trackers for CVE-2018-7160

Affected software / configurations for CVE-2018-7160

References for CVE-2018-7160