CVE-2025-55131

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55130)

Node.js has released security updates addressing multiple vulnerabilities affecting its active release lines (20.x, 22.x, 24.x, 25.x). Key issues include:

1. CVE-2025-55131 (High): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted using the vm module with the timeout option. Buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data, potentially leaking in-process secrets (tokens, passwords) or causing data corruption.
2. CVE-2025-55130 (High): A flaw in Node.js's Permissions model allows attackers to bypass `
3. CVE-2025-59465 (High): A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash due to an unhandled TLSSocket error, leading to a remote denial of service.
4. CVE-2025-59466 (Medium): A bug in Node.js error handling makes "Maximum call stack size exceeded" errors uncatchable when async_hooks.createHook() is enabled, causing the process to terminate unrecoverably.
5. CVE-2025-59464 (Medium): A memory leak in Node.js's OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer during socket.getPeerCertificate(true), allowing remote memory exhaustion.
6. CVE-2026-21636 (Medium): A flaw in Node.js's permission model allows Unix Domain Socket connections to bypass network restrictions even without `
7. CVE-2026-21637 (Medium): A flaw in Node.js TLS error handling allows synchronous exceptions thrown during pskCallback or ALPNCallback to bypass standard error handlers, causing process termination or file descriptor leaks.
8. CVE-2025-55132 (Low): A flaw in Node.js's permission model allows file timestamps to be changed via fs.futimes() even with only read permissions, potentially obscuring activity in logs.(CVE-2025-55131)

A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via futimes() even when the process has only read permissions. Unlike utimes(), futimes() does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55132)

A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash by triggering an unhandled TLSSocket error ECONNRESET. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
  socket.on('error', err => {
    console.log(err)
  })
})
```(CVE-2025-59465)

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded"…

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55130)

Node.js has released security updates addressing multiple vulnerabilities affecting its active release lines (20.x, 22.x, 24.x, 25.x). Key issues include:

1. CVE-2025-55131 (High): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted using the vm module with the timeout option. Buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data, potentially leaking in-process secrets (tokens, passwords) or causing data corruption.
2. CVE-2025-55130 (High): A flaw in Node.js's Permissions model allows attackers to bypass `
3. CVE-2025-59465 (High): A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash due to an unhandled TLSSocket error, leading to a remote denial of service.
4. CVE-2025-59466 (Medium): A bug in Node.js error handling makes "Maximum call stack size exceeded" errors uncatchable when async_hooks.createHook() is enabled, causing the process to terminate unrecoverably.
5. CVE-2025-59464 (Medium): A memory leak in Node.js's OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer during socket.getPeerCertificate(true), allowing remote memory exhaustion.
6. CVE-2026-21636 (Medium): A flaw in Node.js's permission model allows Unix Domain Socket connections to bypass network restrictions even without `
7. CVE-2026-21637 (Medium): A flaw in Node.js TLS error handling allows synchronous exceptions thrown during pskCallback or ALPNCallback to bypass standard error handlers, causing process termination or file descriptor leaks.
8. CVE-2025-55132 (Low): A flaw in Node.js's permission model allows file timestamps to be changed via fs.futimes() even with only read permissions, potentially obscuring activity in logs.(CVE-2025-55131)

A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via futimes() even when the process has only read permissions. Unlike utimes(), futimes() does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55132)

A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash by triggering an unhandled TLSSocket error ECONNRESET. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
  socket.on('error', err => {
    console.log(err)
  })
})
```(CVE-2025-59465)

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded"…

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55130)

Node.js has released security updates addressing multiple vulnerabilities affecting its active release lines (20.x, 22.x, 24.x, 25.x). Key issues include:

1. CVE-2025-55131 (High): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted using the vm module with the timeout option. Buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data, potentially leaking in-process secrets (tokens, passwords) or causing data corruption.
2. CVE-2025-55130 (High): A flaw in Node.js's Permissions model allows attackers to bypass `
3. CVE-2025-59465 (High): A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash due to an unhandled TLSSocket error, leading to a remote denial of service.
4. CVE-2025-59466 (Medium): A bug in Node.js error handling makes "Maximum call stack size exceeded" errors uncatchable when async_hooks.createHook() is enabled, causing the process to terminate unrecoverably.
5. CVE-2025-59464 (Medium): A memory leak in Node.js's OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer during socket.getPeerCertificate(true), allowing remote memory exhaustion.
6. CVE-2026-21636 (Medium): A flaw in Node.js's permission model allows Unix Domain Socket connections to bypass network restrictions even without `
7. CVE-2026-21637 (Medium): A flaw in Node.js TLS error handling allows synchronous exceptions thrown during pskCallback or ALPNCallback to bypass standard error handlers, causing process termination or file descriptor leaks.
8. CVE-2025-55132 (Low): A flaw in Node.js's permission model allows file timestamps to be changed via fs.futimes() even with only read permissions, potentially obscuring activity in logs.(CVE-2025-55131)

A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via futimes() even when the process has only read permissions. Unlike utimes(), futimes() does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55132)

A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash by triggering an unhandled TLSSocket error ECONNRESET. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
  socket.on('error', err => {
    console.log(err)
  })
})
```(CVE-2025-59465)

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded"…

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

A flaw in Node.js’s Permissions model allows attackers to bypass --allow-fs-read and --allow-fs-write restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55130)

Node.js has released security updates addressing multiple vulnerabilities affecting its active release lines (20.x, 22.x, 24.x, 25.x). Key issues include:

1. CVE-2025-55131 (High): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted using the vm module with the timeout option. Buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data, potentially leaking in-process secrets (tokens, passwords) or causing data corruption.
2. CVE-2025-55130 (High): A flaw in Node.js's Permissions model allows attackers to bypass `
3. CVE-2025-59465 (High): A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash due to an unhandled TLSSocket error, leading to a remote denial of service.
4. CVE-2025-59466 (Medium): A bug in Node.js error handling makes "Maximum call stack size exceeded" errors uncatchable when async_hooks.createHook() is enabled, causing the process to terminate unrecoverably.
5. CVE-2025-59464 (Medium): A memory leak in Node.js's OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer during socket.getPeerCertificate(true), allowing remote memory exhaustion.
6. CVE-2026-21636 (Medium): A flaw in Node.js's permission model allows Unix Domain Socket connections to bypass network restrictions even without `
7. CVE-2026-21637 (Medium): A flaw in Node.js TLS error handling allows synchronous exceptions thrown during pskCallback or ALPNCallback to bypass standard error handlers, causing process termination or file descriptor leaks.
8. CVE-2025-55132 (Low): A flaw in Node.js's permission model allows file timestamps to be changed via fs.futimes() even with only read permissions, potentially obscuring activity in logs.(CVE-2025-55131)

A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via futimes() even when the process has only read permissions. Unlike utimes(), futimes() does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.(CVE-2025-55132)

A malformed HTTP/2 HEADERS frame with oversized, invalid HPACK data can cause Node.js to crash by triggering an unhandled TLSSocket error ECONNRESET. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
  socket.on('error', err => {
    console.log(err)
  })
})
```(CVE-2025-59465)

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded"…

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)

• nodejs: Nodejs denial of service (CVE-2026-21637)

• nodejs: Nodejs denial of service (CVE-2025-59466)

• nodejs: Nodejs denial of service (CVE-2025-59465)

• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)

• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

Security Fix(es):

• nodejs: Nodejs filesystem permissions bypass (CVE-2025-55132)
• nodejs: Nodejs denial of service (CVE-2026-21637)
• nodejs: Nodejs denial of service (CVE-2025-59466)
• nodejs: Nodejs denial of service (CVE-2025-59465)
• nodejs: Nodejs uninitialized memory exposure (CVE-2025-55131)
• nodejs: Nodejs file permissions bypass (CVE-2025-55130)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the vm module with the timeout option. Under specific timing conditions, buffers allocated with Buffer.alloc and other TypedArray instances like Uint8Array may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

• CVE-2025-59465: add default error handler to TLSSocket to prevent server crash when connection is abruptly destroyed during initialization
• CVE-2025-59466: fix stack overflow exception handling in async_hooks to allow catching with try-catch instead of requiring uncaughtException handlers
• CVE-2025-55131: refactor unsafe buffer creation to remove zero-fill toggle

• CVE-2025-23167: fix improper termination of HTTP/1 headers using \r\n\rX instead of the required \r\n\r\n.
• CVE-2025-59466: fix uncatchable stack overflow exceptions when async_hooks are enabled, preventing denial-of-service crashes in applications using AsyncLocalStorage or async_hooks.createHook().
• CVE-2025-59465: add TLSSocket default error handler to prevent server crash from unhandled ECONNRESET when a malformed HTTP/2 HEADERS frame with invalid HPACK data abruptly destroys a TLS connection during initialization.
• CVE-2025-55131: refactor unsafe buffer creation to remove zero-fill toggle, preventing exposure of uninitialized memory when buffer allocations are interrupted via the vm module timeout option.

Node.js HTTP/2 server crashes with unhandled error when receiving malformed HEADERS frame. (CVE-2025-59465) Uncatchable "Maximum call stack size exceeded" error on Node.js via async_hooks leads to process crashes bypassing error handlers. (CVE-2025-59466) Bypass File System Permissions using crafted symlinks. (CVE-2025-55130) Timeout-based race conditions make Uint8Array/Buffer.alloc non-zerofilled. (CVE-2025-55131) fs.futimes() Bypasses Read-Only Permission Model. (CVE-2025-55132) TLS PSK/ALPN Callback Exceptions Bypass Error Handlers, Causing DoS and FD Leak. (CVE-2026-21637)