Threadlinqs IntelligenceStart free

Vendor2 products tracked

nodejs vulnerabilities & exploitation

11 with public exploit

As of 2026-11-19, Threadlinqs tracks 49 nodejs CVEs, 0 in the CISA Known Exploited Vulnerabilities catalog, linked to 7 tracked threat campaigns.

CVEs
49Since 2026
CISA KEV
00% of CVEs
Critical
1CVSS v3 9.0+
Avg CVSS
5.7/10Max 10
Threats
7Linked campaigns
Actors
0None attributed

Data as of:

Exploitation timeline

Threadlinqs has recorded 49 nodejs CVEs published between and . The busiest month was 2026-11 (15 new CVEs). None of them is listed in CISA KEV yet.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 49 of 49 tracked nodejs CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 49 CVEs; 2 distinct nodejs products are affected. The most frequently affected:

  • node 47 CVEs
  • Node.js 2 CVEs

Threat activity

7 tracked threat campaigns reference nodejs products or exploit nodejs CVEs:

How to prioritise nodejs patching

This order follows the data Threadlinqs holds for nodejs, not a generic severity checklist:

  • No nodejs CVE is in CISA KEV yet, so rank by exploit probability instead.
  • Outside KEV, the highest EPSS scores are CVE-2026-48933 (3.7%), CVE-2026-48618 (3.2%), CVE-2026-21636 (0.9%).
  • 1 CVE scores Critical and 16 High on CVSS v3 (maximum 10, average 5.7); sequence these after KEV and high-EPSS items.
  • 11 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.