[From nobody Fri Jul 10 09:23:08 2026
Received: (at submit) by bugs.debian.org; 10 Jul 2026 04:31:25 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-10.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 43; hammy, 150; neutral, 69; spammy,
 0. spammytokens: hammytokens:0.000-+--H*F:U*carnil,
 0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--H*Ad:N*Bug,
 0.000-+--H*Ad:N*Tracking
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wi2tX-0013ma-0z
 for submit@bugs.debian.org; Fri, 10 Jul 2026 04:31:25 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: node-tar: CVE-2026-59871 CVE-2026-59873 CVE-2026-59874 CVE-2026-59875
Message-ID: <178365787945.1095134.17758304130054747143.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Fri, 10 Jul 2026 06:31:19 +0200
Delivered-To: submit@bugs.debian.org

Source: node-tar
Version: 7.5.16+~4.0.1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerabilities were published for node-tar.

CVE-2026-59871[0]:
| node-tar is a tar archive manipulation library for Node.js. Prior to
| 7.5.18, node-tar coerces all-digit PAX path and linkpath values in
| src/pax.ts to JavaScript numbers, causing downstream path handling
| such as normalizeWindowsPath(entry.path).split('/') to throw an
| uncaught TypeError. This issue is fixed in version 7.5.18.


CVE-2026-59873[1]:
| node-tar is a tar archive manipulation library for Node.js. Prior to
| 7.5.19, node-tar does not enforce hard upper bounds on total
| decompressed data, entry counts, or decompression ratio in
| extraction and parsing paths such as src/extract.ts, allowing a
| small crafted gzip bomb to exhaust disk space and CPU. This issue is
| fixed in version 7.5.19.


CVE-2026-59874[2]:
| node-tar is a tar archive manipulation library for Node.js. Prior to
| 7.5.18, tar.replace accepts a checksum-valid tar header with a
| negative base-256 encoded entry size, causing the archive scanner to
| make no progress while repeatedly parsing the same header. This
| issue is fixed in version 7.5.18.


CVE-2026-59875[3]:
| node-tar is a tar archive manipulation library for Node.js. Prior to
| 7.5.17, node-tar does not strip NUL bytes from PAX path and linkpath
| records in src/pax.ts, allowing a crafted archive with values to
| reach fs.lstat or fs.open and terminate the process with an uncaught
| exception. This issue is fixed in version 7.5.17.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-59871
    https://www.cve.org/CVERecord?id=CVE-2026-59871
[1] https://security-tracker.debian.org/tracker/CVE-2026-59873
    https://www.cve.org/CVERecord?id=CVE-2026-59873
[2] https://security-tracker.debian.org/tracker/CVE-2026-59874
    https://www.cve.org/CVERecord?id=CVE-2026-59874
[3] https://security-tracker.debian.org/tracker/CVE-2026-59875
    https://www.cve.org/CVERecord?id=CVE-2026-59875

Regards,
Salvatore
]