Outdated Node.js
A server runs a Node.js release that is missing security fixes or whose release line has reached end of life.
| Severity | Medium |
| CVSS 3.1 | 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H Open in the calculator |
| CVSS 4.0 | 8.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1499.004 Application or System Exploitation, T1190 Exploit Public-Facing Application |
| Category | Outdated Components |
Description
A server or application runs a release of Node.js that predates fixes for one or more published vulnerabilities, or a Node.js release line that has reached end of life. The Node.js project issues security releases for all supported release lines together, announced in advance on its blog, and stops fixing each major release line at the end of its planned maintenance period, after which newly disclosed flaws remain exploitable for as long as it is used.
An attacker who can reach the application can exploit the unfixed flaws that its code paths use, so whether a given flaw is exploitable depends on the application using the affected API or feature. Past Node.js vulnerabilities include HTTP request smuggling in the built-in HTTP parser, denial of service through crafted HTTP/2 traffic, flaws in TLS and certificate handling, path traversal and command injection on Windows, and bypasses of the permission model. The typical results are denial of service, which takes the single-threaded application offline, and request smuggling, which can bypass controls enforced by a front-end proxy or poison shared caches; a smaller number of flaws have allowed data exposure or code execution under particular conditions.
The finding is identified by authenticated scans that read the installed version, or with node --version, since Node.js applications rarely announce the runtime version over the network, and scanners report one result per missing security release. Node.js is commonly present in several places on one host: installed from the distribution or from the project's own binaries, through version managers such as nvm, inside container images, and bundled with desktop or development tools, and each copy must be updated separately.
Remediation
Keep each Node.js runtime on a current, supported release:
- Upgrade to the latest release of the release line in use, and move applications on end-of-life lines to an active long-term support (LTS) line, testing dependencies first.
- Rebuild container images on an updated Node.js base image and redeploy them; updating the host does not update its containers.
- Update every copy of Node.js on each host, including those installed by version managers and bundled with tools, and remove those that are not needed.
- Follow the Node.js security release announcements and schedule the update as soon as a release is pre-announced.
- Run the application behind a reverse proxy that normalises HTTP requests and enforces request limits, which reduces exposure to parser and denial of service flaws.
Confirm the fix with node --version on each host and in each image, and by repeating the scan.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.