Node.js ReadFileUtf8 binding leaks memory => DoS
CVE-2025-23165 Published on May 19, 2025

In Node.js, the `ReadFileUtf8` internal binding leaks memory due to a corrupted pointer in `uv_fs_s.file`: a UTF-16 path buffer is allocated but subsequently overwritten when the file descriptor is set. This results in an unrecoverable memory leak on every call. Repeated use can cause unbounded memory growth, leading to a denial of service. Impact: * This vulnerability affects APIs relying on `ReadFileUtf8` on Node.js release lines: v20 and v22.

NVD

Weakness Type

What is a Memory Leak Vulnerability?

The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is often triggered by improper handling of malformed data or unexpectedly interrupted sessions. In some languages, developers are responsible for tracking memory allocation and releasing the memory. If there are no more pointers or references to the memory, then it can no longer be tracked and identified for release.

CVE-2025-23165 has been classified to as a Memory Leak vulnerability or weakness.


Products Associated with CVE-2025-23165

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2025-23165 are published in these products:

 
 

Affected Versions

nodejs node:

Exploit Probability

EPSS
0.09%
Percentile
25.16%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.