Critical Security Update for Node.js Packaging: Denial of Service Vulnerabilities
Summary
RLSA-2026:47060: Important: nodejs:24 security update. Affects nodejs-packaging across 3 version ranges.
< 0:2021.06-6.module+el8.10.0+40048+6d99f608
< 0:2021.06-6.module+el8.10.0+40171+8fa9c325
< 0:2021.06-6.module+el8.10.0+40172+38f6fdd1
Fixed in 0:2021.06-6.module+el8.10.0+40048+6d99f608, 0:2021.06-6.module+el8.10.0+40171+8fa9c325 or 0:2021.06-6.module+el8.10.0+40172+38f6fdd1, depending on the release line you run. How to fix ↓
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.
No signup required · Results in about 60 seconds
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 applications and has a rich ecosystem of libraries and tools. The nodejs-packaging component is crucial for managing Node.js applications in Rocky Linux environments. However, recent vulnerabilities have been identified that could potentially compromise the integrity and availability of applications built on this platform.
Vulnerability Detail
The vulnerabilities identified in Node.js packaging stem from issues in the brace-expansion and tar libraries. Specifically, CVE-2026-13149 presents a Denial of Service (DoS) risk due to exponential-time complexity in brace-expansion. Additionally, CVE-2026-59873 and CVE-2026-59874 expose applications to DoS attacks via malformed tar archive headers and crafted gzip bombs, respectively. These vulnerabilities could lead to significant service disruptions, making it critical for users to address them promptly.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
sudo dnf update nodejs-packaging-
< 0:2021.06-6.module+el8.10.0+40048+6d99f6080:2021.06-6.module+el8.10.0+40048+6d99f608 -
< 0:2021.06-6.module+el8.10.0+40171+8fa9c3250:2021.06-6.module+el8.10.0+40171+8fa9c325 -
< 0:2021.06-6.module+el8.10.0+40172+38f6fdd10:2021.06-6.module+el8.10.0+40172+38f6fdd1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If immediate patching is not feasible, consider implementing rate limiting on your applications to mitigate the impact of potential DoS attacks. Additionally, avoid processing untrusted tar files until the vulnerabilities are addressed.
Conclusion
In summary, the recent vulnerabilities in Node.js packaging pose significant risks, particularly in terms of Denial of Service attacks. It is crucial for users to update their packages to the latest patched versions to ensure the security and stability of their applications. Utilizing tools like Vulert can further enhance your ability to monitor and respond to vulnerabilities effectively.
See every vulnerability recorded for nodejs-packaging →
FAQ
The vulnerabilities have a CVSS score of 7.5, indicating a high severity level that requires prompt attention.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by these vulnerabilities without needing to sign up.
These vulnerabilities can lead to Denial of Service attacks, which may disrupt the availability of your applications and services.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just a manifest file like package-lock.json.
Implementing rate limiting and avoiding the processing of untrusted tar files can help mitigate risks until you can apply the updates.
References
Related vulnerabilities
Recent vulnerabilities recorded for nodejs-packaging.
