SB2026051526 - Debian update for nodejs



SB2026051526 - Debian update for nodejs

Published: May 15, 2026

Security Bulletin ID SB2026051526
CSH Severity
Medium
Patch available
YES
Number of vulnerabilities 8
Exploitation vector Remote access
Highest impact Denial of service

Breakdown by Severity

Medium 88% Low 13%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 8 vulnerabilities.


1) Memory leak (CVE-ID: CVE-2025-23085)

The vulnerability allows a remote attacker to perform DoS attack on the target system.

The vulnerability exists due memory leak when a remote peer abruptly closes the socket without sending a GOAWAY notification. A remote attacker can force the application to leak memory and perform denial of service attack.


2) Improper error handling (CVE-ID: CVE-2025-23166)

The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.

The vulnerability exists due to incorrect error handling in async cryptographic operations within the SignTraits::DeriveBits() function. A remote attacker can send specially crafted input to the application can crash the Node.js runtime.


3) Race condition (CVE-ID: CVE-2025-55131)

The vulnerability allows a remote user to disclose sensitive information or corrupt data.

The vulnerability exists due to a race condition in buffer allocation logic when using the vm module with the timeout option. A remote user can influence workload and timeout behavior to disclose sensitive information or corrupt data.

Exploitation typically requires precise timing or in-process code execution.


4) Uncaught Exception (CVE-ID: CVE-2025-59465)

The vulnerability allows a remote attacker to cause a denial of service.

The vulnerability exists due to improper error handling in the HTTP/2 server when receiving a malformed HEADERS frame with oversized invalid HPACK data. A remote attacker can send a specially crafted HTTP/2 HEADERS frame to cause a denial of service.

This primarily affects applications that do not attach explicit error handlers to secure sockets.


5) Uncaught Exception (CVE-ID: CVE-2025-59466)

The vulnerability allows a remote attacker to cause a denial of service.

The vulnerability exists due to improper error handling in async_hooks error handling when deep recursion occurs with async_hooks.createHook() enabled. A remote attacker can trigger deep recursion to cause a denial of service.

Applications using AsyncLocalStorage or async_hooks.createHook() are affected under specific conditions.


6) Improper error handling (CVE-ID: CVE-2026-21710)

The vulnerability allows a remote attacker to cause a denial of service.

The vulnerability exists due to improper handling of special property names in HTTP headers in req.headersDistinct when parsing incoming HTTP requests. A remote attacker can send a request with a header named __proto__ to trigger a TypeError when the application accesses req.headersDistinct, crashing the Node.js process.

The exception occurs synchronously in a property getter and cannot be caught without wrapping every access in try/catch.


7) Information Exposure Through Timing Discrepancy (CVE-ID: CVE-2026-21713)

The vulnerability allows a remote attacker to potentially forge message authentication codes.

The vulnerability exists due to use of non-constant-time comparison in HMAC verification in crypto_hmac.cc when validating user-provided signatures. A remote attacker can measure timing differences during signature comparison to infer valid HMAC values, acting as a timing oracle.

Exploitation requires high-resolution timing measurements and repeated queries under a favorable threat model.


8) Missing release of memory after effective lifetime (CVE-ID: CVE-2026-21714)

The vulnerability allows a remote attacker to cause resource exhaustion.

The vulnerability exists due to a memory leak in the HTTP/2 server implementation when processing WINDOW_UPDATE frames on stream 0. A remote attacker can send WINDOW_UPDATE frames that exceed the maximum flow control window, causing the Http2Session object to remain allocated despite sending a GOAWAY frame.

The server fails to clean up the Http2Session object after connection termination, leading to unbounded memory consumption.


Remediation

Install update from vendor's website.