nodejs - Debian Package Tracker

general

source: nodejs (main)
version: 22.22.0+dfsg+~cs22.19.6-1
maintainer: Debian Javascript Maintainers (archive) (DMD)
uploaders: Jonas Smedegaard [DMD] – Jérémy Lal [DMD]
arch: all amd64 arm64 armel armhf i386 mips64el powerpc ppc64 ppc64el s390x
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 12.22.12~dfsg-1~deb11u4
o-o-sec: 12.22.12~dfsg-1~deb11u7
oldstable: 18.20.4+dfsg-1~deb12u1
old-sec: 18.20.4+dfsg-1~deb12u1
stable: 20.19.2+dfsg-1
testing: 22.22.0+dfsg+~cs22.19.6-1
unstable: 22.22.0+dfsg+~cs22.19.6-1
exp: 24.13.0+dfsg+~cs24.10.7-2

versioned links

12.22.12~dfsg-1~deb11u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
12.22.12~dfsg-1~deb11u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
18.20.4+dfsg-1~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
20.19.2+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
22.22.0+dfsg+~cs22.19.6-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
24.13.0+dfsg+~cs24.10.7-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libnode-dev (1 bugs: 0, 1, 0, 0)
libnode127
nodejs (11 bugs: 0, 9, 2, 0)
nodejs-doc

action needed

A new upstream version is available: 22.22.0+~cs22.19.9 high

A new upstream version 22.22.0+~cs22.19.9 is available, you should consider packaging it.

Created: 2026-01-18 Last update: 2026-02-10 18:30

6 security issues in trixie high

There are 6 open security issues in trixie.

6 important issues:

CVE-2025-55130: 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-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.
CVE-2025-55132: 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-59465: 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-59466: We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
CVE-2026-21637: A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.

Created: 2026-01-14 Last update: 2026-01-21 06:00

9 security issues in bullseye high

There are 9 open security issues in bullseye.

6 important issues:

CVE-2025-55130: 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-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.
CVE-2025-55132: 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-59465: 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-59466: We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
CVE-2026-21637: A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.

3 ignored issues:

CVE-2023-30581: The use of __proto__ in process.mainModule.__proto__.require() can bypass the policy mechanism and require modules outside of the policy.json definition. This vulnerability affects all users using the experimental policy mechanism in all active release lines: v16, v18 and, v20. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js
CVE-2023-32002: The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32006: The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

Created: 2026-01-14 Last update: 2026-01-21 06:00

8 security issues in bookworm high

There are 8 open security issues in bookworm.

6 important issues:

CVE-2025-55130: 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-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.
CVE-2025-55132: 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-59465: 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-59466: We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
CVE-2026-21637: A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.

2 issues left for the package maintainer to handle:

CVE-2025-23085: (postponed; to be fixed through a stable update) A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.
CVE-2025-23166: (postponed; to be fixed through a stable update) 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.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-02-16 Last update: 2026-01-21 06:00

debian/patches: 1 patch with invalid metadata, 2 patches to forward upstream high

Among the 21 debian patches available in version 22.22.0+dfsg+~cs22.19.6-1 of the package, we noticed the following issues:

1 patch with invalid metadata that ought to be fixed.
2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-01-14 12:18

5 security issues in buster high

There are 5 open security issues in buster.

2 important issues:

CVE-2024-27982: The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first.
CVE-2024-27983: An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.

3 ignored issues:

CVE-2021-44531: Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.
CVE-2021-44532: Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.
CVE-2021-44533: Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.

Created: 2024-04-03 Last update: 2024-06-29 13:15

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-04-04 Last update: 2026-02-10 19:02

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 24.13.0+dfsg+~cs24.10.7-2.1, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 02d16e40855b3537d1029855fa3bc7b39b05d3a9
Merge: d56ca057 1286e36c
Author: Jérémy Lal <kapouer@debian.org>
Date:   Thu Feb 5 07:41:58 2026 +0000

    Merge branch 'debian/latest' into 'debian/latest'
    
    riscv64: Fix sp handling in MacroAssembler::LeaveFrame
    
    See merge request js-team/nodejs!23

commit 1286e36ca5978b31e18936c2f24b0bea30eea017
Author: Han Gao <rabenda.cn@gmail.com>
Date:   Thu Feb 5 07:41:58 2026 +0000

    riscv64: Fix sp handling in MacroAssembler::LeaveFrame

Created: 2026-02-05 Last update: 2026-02-05 08:32

lintian reports 15 warnings normal

Lintian reports 15 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-11-19 Last update: 2026-01-14 18:01

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-01-14 13:01

testing migrations

This package will soon be part of the auto-nodejs transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
This package will soon be part of the auto-icu transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2026-01-20] nodejs 22.22.0+dfsg+~cs22.19.6-1 MIGRATED to testing (Debian testing watch)
[2026-01-14] Accepted nodejs 22.22.0+dfsg+~cs22.19.6-1 (source) into unstable (Jérémy Lal)
[2026-01-13] Accepted nodejs 24.13.0+dfsg+~cs24.10.7-2 (source) into experimental (Jérémy Lal)
[2026-01-13] Accepted nodejs 24.13.0+dfsg+~cs24.10.7-1 (source) into experimental (Jérémy Lal)
[2025-12-20] Accepted nodejs 24.12.0+dfsg+~cs24.10.4-1 (source) into experimental (Jérémy Lal)
[2025-12-20] nodejs 22.21.1+dfsg+~cs22.19.0-6 MIGRATED to testing (Debian testing watch)
[2025-12-15] Accepted nodejs 24.11.1+dfsg+~cs24.10.1-2 (source) into experimental (Jérémy Lal)
[2025-12-11] Accepted nodejs 24.11.1+dfsg+~cs24.10.1-1 (source ppc64el all) into experimental (Debian FTP Masters) (signed by: Jérémy Lal)
[2025-12-07] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-6 (source) into unstable (Jérémy Lal)
[2025-12-07] nodejs 22.21.1+dfsg+~cs22.19.0-5 MIGRATED to testing (Debian testing watch)
[2025-11-21] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-5 (source) into unstable (Jérémy Lal)
[2025-11-19] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-4 (source) into unstable (Jérémy Lal)
[2025-11-11] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-3 (source) into experimental (Jérémy Lal)
[2025-11-10] nodejs 20.19.5+dfsg+~cs20.19.24-1 MIGRATED to testing (Debian testing watch)
[2025-11-10] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-2 (source) into experimental (Jérémy Lal)
[2025-11-09] Accepted nodejs 22.21.1+dfsg+~cs22.19.0-1 (source) into experimental (Jérémy Lal)
[2025-11-05] Accepted nodejs 20.19.5+dfsg+~cs20.19.24-1 (source) into unstable (Jérémy Lal)
[2025-10-13] nodejs 20.19.5+dfsg+~cs20.19.12-4 MIGRATED to testing (Debian testing watch)
[2025-10-08] Accepted nodejs 20.19.5+dfsg+~cs20.19.12-4 (source) into unstable (Jérémy Lal)
[2025-10-06] Accepted nodejs 20.19.5+dfsg+~cs20.19.12-3 (source) into unstable (Jérémy Lal)
[2025-10-06] Accepted nodejs 20.19.5+dfsg+~cs20.19.12-2 (source) into unstable (Jérémy Lal)
[2025-10-05] Accepted nodejs 20.19.5+dfsg+~cs20.19.12-1 (source) into unstable (Jérémy Lal)
[2025-09-25] nodejs 20.19.4+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-08-29] Accepted nodejs 18.20.4+dfsg-1~deb12u1 (source amd64 all) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Jérémy Lal)
[2025-08-29] Accepted nodejs 18.20.4+dfsg-1~deb12u1 (source amd64 all) into oldstable-security (Debian FTP Masters) (signed by: Jérémy Lal)
[2025-08-29] Accepted nodejs 22.19.0+dfsg+~cs22.18.0-1 (source) into experimental (Jérémy Lal)
[2025-08-22] Accepted nodejs 22.18.0+dfsg+~cs22.17.2-2 (source) into experimental (Jérémy Lal)
[2025-08-22] Accepted nodejs 22.18.0+dfsg+~cs22.17.2-1 (source) into experimental (Jérémy Lal)
[2025-08-21] Accepted nodejs 20.19.4+dfsg-1 (source) into unstable (Jérémy Lal)
[2025-08-16] Accepted nodejs 22.18.0+dfsg-1 (source) into experimental (Jérémy Lal)

bugs [bug history graph]

all: 18 19
RC: 2
I&N: 13 14
M&W: 2
F&P: 1
patch: 0

links

homepage
lintian (0, 15)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 22.22.0+dfsg+~cs22.19.6-1ubuntu2
47 bugs (1 patch)
patches for 22.22.0+dfsg+~cs22.19.6-1ubuntu2