CVE-2018-12123 [Medium] | Spoofing in Node.js

Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Node.js application is using url.parse() to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the hostname, they may be incorrect.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	3.94%	4.05%	+0.11%
2	2026-04-18	4.55%	3.94%	-0.61%
3	2026-03-04	—	4.55%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

3.94%

4.05%

+0.11%

2026-04-18

4.55%

3.94%

-0.61%

2026-03-04

—

4.55%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N` 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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:N/I:P/A:N` 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:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	8.6	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N 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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

4.3

2.0

MEDIUM

AV:N/AC:M/Au:N/C:N/I:P/A:N 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:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

8.6

2.9

[email protected]

OS Trackers for CVE-2018-12123

vendor	priority	summary	link
`alpine`	—	CVE-2018-12123: 2 source package rows (nodejs, nodejs-current); 47 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 30.	https://security.alpinelinux.org/vuln/CVE-2018-12123
`debian`	unimportant	CVE-2018-12123 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-12123
`gentoo`	normal	CVE-2018-12123: 1 GLSA(s) (202003-48), 1 atom(s) (net-libs/nodejs); latest impact normal.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2018-12123
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2018-12123
`suse`	medium	CVE-2018-12123 severity moderate: SUSE including 73 source package names (MozillaFirefox-68.2.0-78.51.4, MozillaFirefox-branding-SLED-68-21.9.8, …), 234 product×package rows across 30 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 4, … (30 product lines)): Fixed 167, Known Not Affected 67.	https://www.suse.com/security/cve/CVE-2018-12123/
`ubuntu`	low	CVE-2018-12123 low priority: Ubuntu including 1 source packages (nodejs), 19 status rows across 19 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 14, needed 2, released 2, ignored 1.	https://ubuntu.com/security/CVE-2018-12123

Affected software / configurations for CVE-2018-12123

Vendor	Product	Version	Raw CPE
nodejs	node.js	>= 6.0.0, < 6.15.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 8.0.0, < 8.14.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 10.0.0, < 10.14.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 11.0.0, < 11.3.0	cpe:2.3:a:nodejs:node.js:::::-:::*

References for CVE-2018-12123

URL	Tags
https://access.redhat.com/errata/RHSA-2019:1821	Third Party Advisory
https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/	Patch Vendor Advisory
https://security.gentoo.org/glsa/202003-48	Third Party Advisory
https://security.netapp.com/advisory/ntap-20241213-0008/

URL

CVE-2018-12123

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

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

Weakness enumeration for CVE-2018-12123

OS Trackers for CVE-2018-12123

Affected software / configurations for CVE-2018-12123

References for CVE-2018-12123