High

CVE-2018-12120 — Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any…

Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `node debug`, it listens to port 5858 on all interfaces by default. This may allow remote computers to attach to the debug port and evaluate arbitrary JavaScript. The default interface is now localhost. It has always been possible to start the debugger on a specific interface, such as `node --debug=localhost`. The debugger was removed in Node.js 8 and replaced with the inspector, so no versions from 8 and later are vulnerable.

Published Nov 28, 2018 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nodejs

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 4.3% (30-day exploitation probability)+14
Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

4.28%

ahead of 91% of scored CVEs · Oct 14, 2026

Affects

Nodejs

Node.js

CVSS base

8.1

High · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — nodejs.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Nodejs Node.js, The Node.js Project Node.js).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
Apply the fixed version or the patch documented under Remediation.
EPSS ahead of 91% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Nodejs	Node.js	≥ 6.0.0 and < 6.15.0	Vulnerable	NIST National Vulnerability Database
The Node.js Project	Node.js	version All versions prior to Node.js 6.15.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.1	CVSS 3.1	High	2.2	5.9	nvd@nist.gov via NIST National Vulnerability Database
6.8	CVSS 2.0	Medium	8.6	6.4	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-829

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 4.28%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · the node.js project/node.js
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 8.1
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2018
CVE published
Nov 28, 2018 · nodejs

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

nodejs.org/en/blog/vulnerability/november-2018-security-releases/
Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
www.securityfocus.com/bid/106040
Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database

Elsewhere on this site

Nodejs
every CVE for this vendor

CWE-829
other pages naming this weakness

Related CVEs (same products)

Low CVE-2026-48935 Incorrect Default Permissions in Nodejs Node.js Jun 25, 2026
Low CVE-2026-48936 Improper Access Control in Nodejs Node.js Jun 25, 2026
Medium CVE-2026-48928 Improper Access Control in Nodejs Node.js Jun 25, 2026
Critical CVE-2026-48930 Node.js TLS hostname handling flaw enabling silent authority rebinding Jun 25, 2026
High CVE-2026-48615 A flaw in Node.js proxy tunnel error handling could expose proxy credentials in… Jun 25, 2026
High CVE-2026-48619 Uncontrolled Resource Consumption in Nodejs Node.js Jun 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-12120 is "Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any…", rated High. It affects Node.js (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 4.28% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.