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

Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be "__proto__". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object these properties are being assigned to.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.34%	21.51%	+21.18%
2	2026-04-19	0.66%	0.34%	-0.33%
3	2026-04-03	—	0.66%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.34%

21.51%

+21.18%

2026-04-19

0.66%

0.34%

-0.33%

2026-04-03

—

0.66%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	4.2	[email protected]
6.4	2.0	MEDIUM	`AV:N/AC:L/Au:N/C:N/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	10.0	4.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

4.2

[email protected]

6.4

2.0

MEDIUM

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

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

10.0

4.9

[email protected]

OS Trackers for CVE-2022-21824

vendor	priority	summary	link
`alpine`	high	CVE-2022-21824: 3 source package rows (nodejs, nodejs-current, openjdk11); 82 state rows across 15 repos (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 22, open 60.	https://security.alpinelinux.org/vuln/CVE-2022-21824
`debian`	not yet assigned	CVE-2022-21824 not yet assigned 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-21824
`gentoo`	low	CVE-2022-21824: 1 GLSA(s) (202405-29), 1 atom(s) (net-libs/nodejs); latest impact low.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-21824
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-21824
`suse`	medium	CVE-2022-21824 severity moderate: SUSE including 53 source package names (12-10.1:nodejs12-12.22.9-4.25.1, 12-10.1:npm12-12.22.9-4.25.1, …), 221 product×package rows across 35 product lines (Container bci/nodejs, SUSE CaaS Platform 4.0, … (35 product lines)): Fixed 181, Known Not Affected 40.	https://www.suse.com/security/cve/CVE-2022-21824/
`ubuntu`	medium	CVE-2022-21824 medium priority: Ubuntu including 1 source packages (nodejs), 13 status rows across 13 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, trusty, upstream, xenial): not-affected 10, ignored 2, released 1.	https://ubuntu.com/security/CVE-2022-21824

Affected software / configurations for CVE-2022-21824

Vendor	Product	Version	Raw CPE
nodejs	node.js	>= 12.0.0, < 12.22.9	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 14.0.0, < 14.18.3	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 16.0.0, < 16.13.2	cpe:2.3:a:nodejs:node.js:::::lts:::*
nodejs	node.js	>= 17.0.0, < 17.3.1	cpe:2.3:a:nodejs:node.js:::::-:::*
oracle	mysql_cluster	<= 8.0.29	cpe:2.3:a:oracle:mysql_cluster::::::::
oracle	mysql_connectors	<= 8.0.28	cpe:2.3:a:oracle:mysql_connectors::::::::
oracle	mysql_enterprise_monitor	<= 8.0.29	cpe:2.3:a:oracle:mysql_enterprise_monitor::::::::
oracle	mysql_server	<= 8.0.29	cpe:2.3:a:oracle:mysql_server::::::::
oracle	mysql_workbench	<= 8.0.28	cpe:2.3:a:oracle:mysql_workbench::::::::
oracle	peoplesoft_enterprise_peopletools	8.58	cpe:2.3:a:oracle:peoplesoft_enterprise_peopletools:8.58:::::::*
oracle	peoplesoft_enterprise_peopletools	8.59	cpe:2.3:a:oracle:peoplesoft_enterprise_peopletools:8.59:::::::*
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*
netapp	oncommand_insight	—	cpe:2.3:a:netapp:oncommand_insight:-:::::::*
netapp	oncommand_workflow_automation	—	cpe:2.3:a:netapp:oncommand_workflow_automation:-:::::::*
netapp	snapcenter	—	cpe:2.3:a:netapp:snapcenter:-:::::::*

References for CVE-2022-21824

URL	Tags
https://hackerone.com/reports/1431042	Issue Tracking Mitigation Third Party Advisory
https://lists.debian.org/debian-lts-announce/2022/10/msg00006.html	Mailing List Third Party Advisory
https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/	Release Notes Vendor Advisory
https://security.netapp.com/advisory/ntap-20220325-0007/	Third Party Advisory
https://security.netapp.com/advisory/ntap-20220729-0004/	Third Party Advisory
https://www.debian.org/security/2022/dsa-5170	Third Party Advisory
https://www.oracle.com/security-alerts/cpuapr2022.html	Patch Third Party Advisory
https://www.oracle.com/security-alerts/cpujul2022.html	Third Party Advisory

URL

CVE-2022-21824

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

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

Weakness enumeration for CVE-2022-21824

OS Trackers for CVE-2022-21824

Affected software / configurations for CVE-2022-21824

References for CVE-2022-21824