[From nobody Sat Aug  8 10:06:04 2026
Received: (at submit) by bugs.debian.org; 31 Jul 2026 11:58:27 +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=-9.9 required=4.0 tests=BAYES_00, FOURLA,
 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, 35; hammy, 150; neutral, 90; 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 1wplsg-0027w2-1j
 for submit@bugs.debian.org; Fri, 31 Jul 2026 11:58:27 +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-re2: CVE-2026-68499 CVE-2026-67550
Message-ID: <178549910021.1841829.4949263500417992693.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Fri, 31 Jul 2026 13:58:20 +0200
Delivered-To: submit@bugs.debian.org

Source: node-re2
Version: 1.25.0+~cs1.6.0-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-re2.

CVE-2026-68499[0]:
| re2 provides Node.js bindings for Google's RE2 regular expression
| engine. Prior to 1.25.2, re2's String.prototype.match implementation
| with a global RE2 pattern that can match the empty string fails to
| advance its native matching cursor in lib/match.cc, causing an
| infinite loop and unbounded native memory growth that blocks the
| event loop and can exhaust host memory. This issue is fixed in
| 1.25.2.


CVE-2026-67550[1]:
| re2 provides Node.js bindings for Google's RE2 regular expression
| engine. Prior to 1.25.2, re2 validates lastIndex against the UTF-8
| byte length of a subject but uses it as a UTF-16 code-unit offset in
| exec, test, match, replace, and split, allowing an attacker-
| influenced lastIndex on a non-ASCII subject to trigger an out-of-
| bounds heap read and an uncatchable process crash, with limited heap
| information disclosure in some cases. This issue is fixed in 1.25.2.


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-68499
    https://www.cve.org/CVERecord?id=CVE-2026-68499
    https://github.com/uhop/node-re2/security/advisories/GHSA-6hxr-mr5r-9836
[1] https://security-tracker.debian.org/tracker/CVE-2026-67550
    https://www.cve.org/CVERecord?id=CVE-2026-67550
    https://github.com/uhop/node-re2/security/advisories/GHSA-ff84-5f28-78qj

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]