Blog: post release announcement May security releases

Author: RafaelGSS

apps/site/pages/en/blog/vulnerability/may-2025-security-releases.md

@@ -1,12 +1,60 @@
 ---
-date: 2025-05-08T03:00:00.000Z
+date: 2025-05-14T03:00:00.000Z
 category: vulnerability
 title: Wednesday, May 14, 2025 Security Releases
 slug: may-2025-security-releases
 layout: blog-post
 author: The Node.js Project
 ---
 
+## Security releases available
+
+Updates are now available for the 24.x, 23.x, 22.x, 20.x Node.js release lines for the
+following issues.
+
+## Improper error handling in async cryptographic operations crashes process (CVE-2025-23166) - (high)
+
+The C++ method `SignTraits::DeriveBits()` may incorrectly call `ThrowException()`
+based on user-supplied inputs when executing in a background thread, crashing the Node.js process.
+Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism
+potentially allows an adversary to remotely crash a Node.js runtime.
+
+Impact:
+
+- This vulnerability affects all users in active release lines: 20.x, 22.x, 23.x, 24.x
+
+Thank you, @panva and @tniessen, for reporting and fixing this vulnerability.
+
+## Improper HTTP header block termination in llhttp (CVE-2025-23167) - (medium)
+
+A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
+This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests.
+
+The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination.
+
+Impact:
+
+- This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.
+
+Thank you, to kenballus for reporting this vulnerability and thank you RafaelGSS for fixing it.
+
+## Corrupted pointer in `node::fs::ReadFileUtf8(const FunctionCallbackInfo<Value>& args)` when `args[0]` is a string. (CVE-2025-23165) - (low)
+
+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.
+
+Thank you, to Justin Nietzel for reporting and fixing this vulnerability.
+
+## Downloads and release details
+
+- [Node.js v20.19.2](/blog/release/v20.19.2/)
+- [Node.js v22.15.1](/blog/release/v22.15.1/)
+- [Node.js v23.11.1](/blog/release/v23.11.1/)
+- [Node.js v24.0.1](/blog/release/v24.0.1/)
+
 # Summary
 
 The Node.js project will release new versions of the 24.x, 23.x, 22.x, 20.x

apps/site/site.json

@@ -28,9 +28,9 @@
   ],
   "websiteBanners": {
     "index": {
-      "startDate": "2025-05-08T03:00:00.000Z",
-      "endDate": "2025-05-15T03:00:00.000Z",
-      "text": "New security releases to be made available Wednesday, May 14, 2025",
+      "startDate": "2025-05-14T03:00:00.000Z",
+      "endDate": "2025-05-21T03:00:00.000Z",
+      "text": "May Security Release is available",
       "link": "https://nodejs.org/en/blog/vulnerability/may-2025-security-releases",
       "type": "warning"
     }