Node.js up to 22.22.3/24.16.0/26.3.0 toctou

Summaryinfo

A vulnerability classified as problematic has been found in Node.js up to 22.22.3/24.16.0/26.3.0. The impacted element is an unknown function. Performing a manipulation results in toctou. This vulnerability is cataloged as CVE-2026-48931. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Node.js up to 22.22.3/24.16.0/26.3.0. This affects some unknown processing. The manipulation with an unknown input leads to a toctou vulnerability. CWE is classifying the issue as CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. This is going to have an impact on integrity. The summary by CVE is:

A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

It is possible to read the advisory at nodejs.org. This vulnerability is uniquely identified as CVE-2026-48931 since 05/26/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 321741 (Linux Distros Unpatched Vulnerability : CVE-2026-48931), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (321741). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• Node.js

Version

• 22.22.0
• 22.22.1
• 22.22.2
• 22.22.3
• 24.0
• 24.1
• 24.2
• 24.3
• 24.4
• 24.5
• 24.6
• 24.7
• 24.8
• 24.9
• 24.10
• 24.11
• 24.12
• 24.13
• 24.14
• 24.15
• 24.16.0
• 26.0
• 26.1
• 26.2
• 26.3.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion