Critical Security Update for Node.js: Denial of Service Vulnerabilities

nodejs Updated 17 Apr 2026

Summary

15/04/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:8339: Important: nodejs:20 security update. Affects nodejs versions < 1:20.20.2-1.module_el8.10.0+4165+3f200bda. Fixed in 1:20.20.2-1.module_el8.10.0+4165+3f200bda. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Node.js is a powerful software development platform designed for building fast and scalable network applications using JavaScript. It is widely used for server-side development and offers a rich ecosystem of libraries and tools. However, recent vulnerabilities have been identified that could lead to denial of service attacks, impacting the availability and reliability of applications built on this platform.

Vulnerability Detail

The vulnerabilities stem from issues in the minimatch and nghttp2 libraries, which are integral to Node.js. Specifically, the minimatch library is susceptible to denial of service attacks through specially crafted glob patterns and catastrophic backtracking in glob expressions. Additionally, the nghttp2 library can be exploited via malformed HTTP/2 frames after session termination. Furthermore, a crafted HTTP 'proto' header in Node.js can also lead to denial of service. These vulnerabilities could allow attackers to disrupt service, potentially leading to significant downtime and loss of user trust.

How To Fix

Minimum fixed version

1:20.20.2-1.module_el8.10.0+4165+3f200bda

This is the first release that contains the fix.

sudo dnf update nodejs

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate patching is not feasible, consider implementing rate limiting on your application to mitigate the impact of potential denial of service attacks. This can be done by configuring your server to limit the number of requests from a single IP address over a specified time period.

Conclusion

In summary, the recent vulnerabilities in Node.js pose significant risks, particularly related to denial of service attacks. It is crucial for developers and system administrators to update their Node.js installations and related packages to the latest patched versions to ensure the security and reliability of their applications. Utilizing tools like Vulert can help in monitoring and managing these vulnerabilities effectively.

See every vulnerability recorded for nodejs →

Share this vulnerability

FAQ

The vulnerabilities primarily involve denial of service attacks that can be executed through crafted inputs, affecting the availability of applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.

Failure to address these vulnerabilities can lead to service disruptions, downtime, and potential loss of user trust, which can significantly impact your application's reputation.

Yes, versions prior to 1:20.20.2-1.module_el8.10.0+4165+3f200bda are vulnerable and should be updated to the latest patched version.

If you cannot update immediately, consider implementing rate limiting and monitoring your application for unusual activity to mitigate potential attacks.

Related vulnerabilities

Recent vulnerabilities recorded for nodejs.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

1:20.20.2-1.module_el8.10.0+4165+3f200bda

This is the first release that contains the fix.

sudo dnf update nodejs

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback