[From nobody Thu Jul 30 14:07:09 2026
Received: (at submit) by bugs.debian.org; 30 Jul 2026 05:37:31 +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.9 required=4.0 tests=BAYES_00,FOURLA,
 FROMDEVELOPER,MD5_SHA1_SUM,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, 26; hammy, 150; neutral, 84; spammy,
 0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wpJSU-00FgGW-0O
 for submit@bugs.debian.org; Thu, 30 Jul 2026 05:37:31 +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-body-parser: CVE-2026-12590
Message-ID: <178538984914.1164144.12283438330886518995.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Thu, 30 Jul 2026 07:37:29 +0200
Delivered-To: submit@bugs.debian.org

Source: node-body-parser
Version: 2.2.2+~1.19.6-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for node-body-parser.

CVE-2026-12590[0]:
| Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0
| (2.x line), when the parser is configured with an invalid limit
| option value such as an unparseable string or NaN, bytes.parse
| returns null and the request body size check is silently skipped.
| Applications that rely on limit as their primary safeguard against
| oversized request bodies will accept arbitrarily large payloads,
| leading to excessive memory and CPU usage and denial of service.
| Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After
| the fix, invalid limit values throw a clear error at parser
| construction time instead of silently disabling enforcement, while
| null and undefined continue to fall back to the default limit of
| 100kb. Workarounds: Validate the limit value before passing it to
| body-parser. For example, parse the value at startup and reject any
| configuration where the result is null or a non-finite number.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-12590
    https://www.cve.org/CVERecord?id=CVE-2026-12590
[1] https://github.com/expressjs/body-parser/security/advisories/GHSA-v422-hmwv-36x6
[2] https://github.com/expressjs/body-parser/pull/698
[3] https://github.com/expressjs/body-parser/commit/2322e111cc321413ec2b7b76d01be533d3de9d7d

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]