CVE-2025-23165
Node.js 20 and 1 other: Missing Release of Memory after Effective Lifetime
CVE-2025-23165 is fixed in 32 products on 2 platforms, first by Node.js 20 20.19.2, released May 14, 2025. It is not reported as exploited. Patch Radar priority: High.
HighFixed on 2 platforms
CVSS
7.5
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0056
46th percentile
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Windows apps | |||
| Node.js 20 | 20.19.2 | Node.js 20 20.19.2 | May 14, 2025 |
| Node.js 22 | 22.15.1 | Node.js 22 22.15.1 | May 14, 2025 |
| Linux | |||
| nodejs · Debian 13.5 (trixie) | 20.19.2+dfsg-1 | DEBIAN-CVE-2025-23165 | May 19, 2025 |
| nodejs · Debian 14 | 20.19.2+dfsg-1 | DEBIAN-CVE-2025-23165 | May 19, 2025 |
| nodejs · RHEL 8 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs · RHEL 9 | 1:20.19.2-1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs · almalinux 8 | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs · ol 10 | 1:22.16.0-1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs · rocky 8 | 1:20.19.2-1.module+el8.10.0+1988+437f3d23 | RLSA-2025:8514 | Jul 29, 2025 |
| nodejs · rocky 9 | 1:20.19.2-1.module+el9.6.0+32143+ae966e5b | RLSA-2025:8468 | Jul 29, 2025 |
| nodejs-devel · RHEL 8 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-devel · RHEL 9 | 1:20.19.2-1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-devel · almalinux 8 | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs-devel · ol 10 | 1:22.16.0-1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs-docs · RHEL 8 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-docs · RHEL 9 | 1:20.19.2-1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-docs · almalinux 8 | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs-docs · ol 10 | 1:22.16.0-1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs-full-i18n · RHEL 8 | 1:20.19.2-1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-full-i18n · RHEL 9 | 1:20.19.2-1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-full-i18n · almalinux 8 | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs-full-i18n · ol 10 | 1:22.16.0-1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs-libs · RHEL 8 | 1:22.16.0-1.module+el8.10.0+23140+4056b950 | RHSA-2025:8506 | Jun 4, 2025 |
| nodejs-libs · RHEL 9 | 1:22.16.0-1.module+el9.6.0+23151+b1496e9d | RHSA-2025:8467 | Jun 3, 2025 |
| nodejs-libs · ol 10 | 1:22.16.0-1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs-nodemon · RHEL 8 | 0:3.0.1-1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-nodemon · RHEL 9 | 0:3.0.1-1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-nodemon · almalinux 8 | 3.0.1-1.module_el8.10.0+3982+85c136aa | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs-nodemon · rocky 8 | 0:3.0.1-1.module+el8.10.0+1988+437f3d23 | RLSA-2025:8514 | Jul 29, 2025 |
| nodejs-nodemon · rocky 9 | 0:3.0.1-1.module+el9.5.0+31770+0da7192d | RLSA-2025:8468 | Jul 29, 2025 |
| nodejs-npm · ol 10 | 1:10.9.2-1.22.16.0.1.el10_0 | ELSA-2025-8493 | Jun 27, 2025 |
| nodejs-packaging · RHEL 8 | 0:2021.06-4.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-packaging · RHEL 9 | 0:2021.06-4.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-packaging · almalinux 8 | 2021.06-4.module_el8.10.0+3987+dbda4426 | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs-packaging · rocky 8 | 0:2021.06-4.module+el8.10.0+1667+4a788d89 | RLSA-2025:8514 | Jul 29, 2025 |
| nodejs-packaging · rocky 9 | 0:2021.06-4.module+el9.5.0+31770+0da7192d | RLSA-2025:8468 | Jul 29, 2025 |
| nodejs-packaging-bundler · RHEL 8 | 0:2021.06-4.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| nodejs-packaging-bundler · RHEL 9 | 0:2021.06-4.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| nodejs-packaging-bundler · almalinux 8 | 2021.06-4.module_el8.10.0+3958+472a6467 | ALSA-2025:8514 | Jun 4, 2025 |
| nodejs20 · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20 · opensuse-leap 15.6 | 20.19.2-150600.3.12.1 | SUSE-SU-2025:02045-1 | Jun 20, 2025 |
| nodejs20 · sles 15.6 | 20.19.2-150600.3.12.1 | SUSE-SU-2025:02045-1 | Jun 20, 2025 |
| nodejs20-debuginfo · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-debugsource · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-devel · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-docs · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-full-i18n · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-libs · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-libs-debuginfo · amzn 2023 | 1:20.19.2-1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs20-npm · amzn 2023 | 1:10.8.2-1.20.19.2.1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| nodejs22 · RHEL 10 | 22.16.0-1.el10_0 | RHSA-2025:8493 | May 19, 2025 |
| nodejs22 · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22 · opensuse-leap 15.6 | 22.15.1-150600.13.9.1 | SUSE-SU-2025:01878-1 | Jun 11, 2025 |
| nodejs22 · rocky 10 | 1:22.16.0-1.el10_0 | RLSA-2025:8493 | Oct 3, 2025 |
| nodejs22 · sles 15.6 | 22.15.1-150600.13.9.1 | SUSE-SU-2025:01878-1 | Jun 11, 2025 |
| nodejs22 · sles 15.7 | 22.15.1-150700.3.3.1 | SUSE-SU-2025:01879-1 | Jun 11, 2025 |
| nodejs22-debuginfo · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-debugsource · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-devel · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-docs · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-full-i18n · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-libs · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-libs-debuginfo · amzn 2023 | 1:22.16.0-1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| nodejs22-npm · amzn 2023 | 1:10.9.2-1.22.16.0.1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
| npm · RHEL 8 | 1:10.8.2-1.20.19.2.1.module+el8.10.0+23139+21ba74c5 | RHSA-2025:8514 | Jun 4, 2025 |
| npm · RHEL 9 | 1:10.8.2-1.20.19.2.1.module+el9.6.0+23146+be9976bd | RHSA-2025:8468 | Jun 3, 2025 |
| npm · almalinux 8 | 1:10.8.2-1.20.19.2.1.module_el8.10.0+4007+01f7d99b | ALSA-2025:8514 | Jun 4, 2025 |
| v8-11.3-devel · amzn 2023 | 3:11.3.244.8-1.20.19.2.1.amzn2023.0.1 | ALAS2023-2025-1010 | Jun 4, 2025 |
| v8-12.4-devel · RHEL 8 | 3:12.4.254.21-1.22.16.0.1.module+el8.10.0+23140+4056b950 | RHSA-2025:8506 | Jun 4, 2025 |
| v8-12.4-devel · RHEL 9 | 3:12.4.254.21-1.22.16.0.1.module+el9.6.0+23151+b1496e9d | RHSA-2025:8467 | Jun 3, 2025 |
| v8-12.4-devel · amzn 2023 | 3:12.4.254.21-1.22.16.0.1.amzn2023.0.1 | ALAS2023-2025-1009 | Jun 4, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.