Daily · Article 01 · 3 min read
- Security
- Open source
Node.js releases three security updates. How to check your running server
Node.js advisory dated November 11 · November 12 JST release records
Summary
Node.js released security fixes for its 22, 24 and 26 branches. A deployment example shows how to check whether the servers handling requests are running the fix.
Key facts
Node.js runs JavaScript programs on systems such as web servers. In its advisory dated November 11, the Node.js project announced security releases for the 22, 24 and 26 branches. The update addresses high-severity flaws that can stop a server process or expose data from another connection. The release records and downloadable builds were available on November 12 JST. If you operate a service, start with the version handling requests now. The fixed releases are 22.23.5, 24.22.3 and 26.13.1. The advisory does not report confirmed exploitation. Security advisory Official download index

1. What handles a request behind the browser?
When a customer opens an order page, the browser asks the shop’s server for order details. A shop that uses Node.js may rely on it to manage connections and run the application that finds the order. HTTPS encrypts the exchange, and HTTP/2 lets multiple requests use a connection. When the same program prepares responses for several customers at once, the data for each connection needs to stay separate. The advisory describes an HTTPS flaw where the server can read a temporary workspace it already released, allowing data from another connection to get mixed in. The HTTP/2 flaw can stop the process if an internal check fails while it is closing a connection.
The order page is an example. Actual exposure depends on which protocols the service uses and how its servers are configured. These two findings are among several fixes in the release. Affected branches and impacts
| Advisory finding | What it could mean for an order page | Branches named in the advisory |
|---|---|---|
| Possible HTTPS data exposure, CVE-2026-123864 | Data the server was processing for another connection could be exposed | 22.x · 24.x · 26.x |
| Possible HTTP/2 server crash, CVE-2026-123863 | The process serving order requests could stop | 24.x · 26.x |
- Advisory finding
Possible HTTPS data exposure, CVE-2026-123864
- What it could mean for an order page
- Data the server was processing for another connection could be exposed
- Branches named in the advisory
- 22.x · 24.x · 26.x
- Advisory finding
Possible HTTP/2 server crash, CVE-2026-123863
- What it could mean for an order page
- The process serving order requests could stop
- Branches named in the advisory
- 24.x · 26.x
The cat asks Q&A
- The researcher
If my shop address starts with HTTPS, does that tell me I’m affected?
Pocket NotebookFind out where the encrypted connection is handled. The hosting provider may handle HTTPS before a request reaches Node.js, so ask your operator which system handles HTTPS or HTTP/2 and which version it runs.
2. When the fixed package is ready but an older copy is running
Imagine an order service with two servers. Its operator builds a new container image, a bundle of the files needed to run the program, with the fixed version of Node.js. If the operator replaces only one server, order requests reaching the other still run on the previous version. The deployment record and both servers’ startup logs can show where the fix is running.
%% From release to serving requests · hypothetical deployment
flowchart TD
A["Node.js project · Fix released"] --> B["Provider · Check if update is available"]
B --> C["Operator · Replace both servers"]
C --> D["Startup logs · Check both versions"]The cat asks Q&A
- The researcher
The deployment message says the new image was built. Is that enough?
Pocket NotebookIt shows that the image is ready. To confirm the fix is live, check that the service restarted on the new image and read the running version on every server receiving requests.
3. Which release matches the branch you run?
22.x, 24.x and 26.x are branches identified by the first number in the version. Each has its own fix, so an operator can update within the current branch. These are the upstream versions published by the Node.js project. If an operating system or hosting provider supplies its own package, check that provider’s package version and deployment record.
| Branch in use | Fixed upstream release | Release record |
|---|---|---|
| 22.x | 22.23.5 | 22.23.5 release |
| 24.x | 24.22.3 | 24.22.3 release |
| 26.x | 26.13.1 | 26.13.1 release |
- Branch in use
22.x
- Fixed upstream release
- 22.23.5
- Release record
- 22.23.5 release
- Branch in use
24.x
- Fixed upstream release
- 24.22.3
- Release record
- 24.22.3 release
- Branch in use
26.x
- Fixed upstream release
- 26.13.1
- Release record
- 26.13.1 release
The cat asks Q&A
- The researcher
My development laptop shows 24.22.3. Does that cover the production server?
Pocket NotebookThat tells you the laptop’s version. Check the startup version and deployment time in the container or hosting environment that serves real requests.
To close
Close the update with a running version
If you run the service, check the running version across the servers that receive traffic. If a provider runs it for you, ask which package or image contains the fix, when it was applied, and what version is running. The project’s release record tells you what is available. Your service’s records tell you what is in use.
Sources
- Affected branches and impactsnodejs.org
- Official download indexnodejs.org
- 22.23.5 releasenodejs.org
- 24.22.3 releasenodejs.org
- 26.13.1 releasenodejs.org