CVE-2022-32223 [High] | Security Vulnerability in Node.js

Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows machine:* OpenSSL has been installed and “C:\Program Files\Common Files\SSL\openssl.cnf” exists.Whenever the above conditions are present, `node.exe` will search for `providers.dll` in the current user directory.After that, `node.exe` will try to search for `providers.dll` by the DLL Search Order in Windows.It is possible for an attacker to place the malicious file `providers.dll` under a variety of paths and exploit this vulnerability.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-19	1.54%	1.60%	+0.06%
2	2026-06-15	8.11%	1.54%	-6.57%
3	2026-05-13	—	8.11%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-19

1.54%

1.60%

+0.06%

2026-06-15

8.11%

1.54%

-6.57%

2026-05-13

—

8.11%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.3	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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:L) A normal user session is enough; they don’t have to be admin. 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.	1.3	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.3

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:L): A normal user session is enough; they don’t have to be admin.
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.

1.3

5.9

[email protected]

OS Trackers for CVE-2022-32223

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-32223 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-2022-32223
`suse`	high	CVE-2022-32223 severity important: SUSE including 28 source package names (nodejs10, nodejs10-devel, …), 192 product×package rows across 24 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (24 product lines)): Known Not Affected 192.	https://www.suse.com/security/cve/CVE-2022-32223/
`ubuntu`	medium	CVE-2022-32223 medium priority: Ubuntu including 1 source packages (nodejs), 10 status rows across 10 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, trusty, upstream, xenial): not-affected 7, ignored 2, needs-triage 1.	https://ubuntu.com/security/CVE-2022-32223

Affected software / configurations for CVE-2022-32223

Vendor	Product	Version	Raw CPE
nodejs	node.js	>= 14.0.0, <= 14.14.0	cpe:2.3:a:nodejs:node.js:::::-:::*
nodejs	node.js	>= 14.14.0, < 14.20.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 16.0.0, <= 16.12.0	cpe:2.3:a:nodejs:node.js:::::-:::*
nodejs	node.js	>= 16.13.0, < 16.16.0	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 18.0.0, < 18.0.5	cpe:2.3:a:nodejs:node.js:::::-:::*

References for CVE-2022-32223

URL	Tags
https://hackerone.com/reports/1447455	Permissions Required
https://nodejs.org/en/blog/vulnerability/july-2022-security-releases/	Patch Vendor Advisory
https://security.netapp.com/advisory/ntap-20220915-0001/	Third Party Advisory

URL

CVE-2022-32223

Exploit prediction scoring system (EPSS) score for CVE-2022-32223

Common vulnerability scoring system (CVSS) metrics for CVE-2022-32223

Weakness enumeration for CVE-2022-32223

OS Trackers for CVE-2022-32223

Affected software / configurations for CVE-2022-32223

References for CVE-2022-32223