Is Node.js * vulnerable?
Node.js *, a release of the Node.js runtime. All 3 versions we track · Node.js releases
This project uses Node.js, but AIssue could not tell which exact version runs, so it may be affected by this vulnerability. Check the version you run (on servers, in containers and in CI) and, if the advisory lists it, upgrade.
Known vulnerabilities in Node.js *
-
High
CVSS 7.5
CVE-2026-123866: A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer.
CVE-2026-123866 · published 11 Nov 2026 · no fixed version yet
How to fix it
Check the version you run:
node --version
- Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.
- To have AIssue check the exact version, commit a version file (.java-version, .nvmrc, .python-version, .ruby-version, global.json, .tool-versions...) or pin the full version in your Dockerfile's FROM line.
Other versions of node
Newest version we track without known advisories: 22.23.5.
Licence
Not looked up yet.
Check your whole project
node is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.
About this data
Vulnerability data: the NVD, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.