Node.js vulnerabilities: known CVEs & security history
OpenJS Foundation · Web / Runtime · 30 tracked CVEs · 1 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Node.js release lines — 30 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Node.js's current status and the safe version to run.
Known Node.js CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2026-48930 | critical | 9.8 | 0% | 2026 |
| CVE-2016-9841 | critical | 9.8 | 8% | 2017 |
| CVE-2025-55130 | critical | 9.1 | 2% | 2026 |
| CVE-2016-9842 | high | 8.8 | 5% | 2017 |
| CVE-2016-9840 | high | 8.8 | 5% | 2017 |
| CVE-2026-58043 | high | 8.4 | 0% | 2026 |
| CVE-2026-48617 | high | 8.2 | 0% | 2026 |
| CVE-2026-48933 | high | 7.5 | 4% | 2026 |
| CVE-2026-48619 | high | 7.5 | 1% | 2026 |
| CVE-2026-48615 | high | 7.5 | 0% | 2026 |
| CVE-2026-48937 | high | 7.5 | 1% | 2026 |
| CVE-2026-21710 | high | 7.5 | 26% | 2026 |
| CVE-2025-59465 | high | 7.5 | 4% | 2026 |
| CVE-2017-14919 | high | 7.5 | 8% | 2017 |
| CVE-2026-48618 | medium | 6.5 | 3% | 2026 |
| CVE-2026-21712 | medium | 6.5 | 0% | 2026 |
| CVE-2026-56847 | medium | 6.1 | 0% | 2026 |
| CVE-2026-21717 | medium | 5.9 | 0% | 2026 |
| CVE-2026-21713 | medium | 5.9 | 0% | 2026 |
| CVE-2026-48928 | medium | 5.4 | 0% | 2026 |
| CVE-2026-21714 | medium | 5.3 | 0% | 2026 |
| CVE-2026-21711 | medium | 5.3 | 0% | 2026 |
| CVE-2026-56850 | medium | 4.4 | 0% | 2026 |
| CVE-2026-48934 | medium | 4.3 | 0% | 2026 |
| CVE-2026-48931 | low | 3.7 | 0% | 2026 |
| CVE-2026-48936 | low | 3.3 | 0% | 2026 |
| CVE-2026-48935 | low | 3.3 | 0% | 2026 |
| CVE-2026-21716 | low | 3.3 | 0% | 2026 |
| CVE-2026-21715 | low | 3.3 | 0% | 2026 |
Is my Node.js version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Node.js version → · Monitor Node.js for new CVEs →
Node.js vulnerabilities — frequently asked
How many known vulnerabilities does Node.js have?
IsItPatched tracks 30 CVEs for Node.js, 1 of which is actively exploited (CISA KEV). 3 are critical-severity and 12 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Node.js have any actively-exploited vulnerabilities?
Yes — 1 Node.js CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild. Patch it as a priority.
What is the most severe Node.js vulnerability?
Among tracked issues, CVE-2023-44487 (HIGH, CVSS 7.5), which is actively exploited, ranks highest — a Uncontrolled resource consumption weakness.
Is Node.js safe to use?
It depends on the version. The latest supported Node.js release (26.7.0) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Node.js security status · Node.js end-of-life · actively-exploited CVEs. Always verify against OpenJS Foundation's advisories — see our disclaimer.