[From nobody Tue Nov  3 11:51:06 2026
Received: (at submit) by bugs.debian.org; 31 Oct 2026 09:56:49 +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=-108.1 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
 FOURLA,FROMDEVELOPER,MD5_SHA1_SUM,SPF_HELO_NONE,SPF_PASS,
 USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 42; hammy, 150; neutral, 96; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <carnil@debian.org>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:34206)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <carnil@debian.org>) id 1xN5pR-007O4m-2v
 for submit@bugs.debian.org; Sat, 31 Oct 2026 09:56:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=lZmk+8kmRq57JoCzfXgYH3PwOZqFTDVS5MWXHdw4OHc=; b=d3YcouSQpDL6hD8kviMdA5t4Nl
 cZKfQE9fBOc5Bu3wSB4j27tUpQsjddUBrjl60In8C7B7mFPL36eBaGp3aSTudvAtU05B+z3UguAhi
 9tP6Ua6/R1D1Xm/aHXyTwUENoAD3UEkt866V33ttwCrXOSOKkGMoC4ENh/bBlGpObVLzd9OrkFpbA
 kV/H1b2QhdaqIyk5rVm5wr4Q4WVdVz+iYQ6cSeGZa0LzRW+s/7u6iB4m1tDaipMBuP7K75q+omRz/
 5X25xy2Au4GOZbHMxhqx8dqYHaYxxYQQPDoJ5ROTivnWe3UAPgHnjWVGvzBk2sBzXHPMgCAJe1YdO
 iUwNaTZA==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <carnil@debian.org>) id 1xN5pP-004W0L-2G
 for submit@bugs.debian.org; Sat, 31 Oct 2026 09:56:48 +0000
Received: by eldamar.lan (Postfix, from userid 1000)
 id 51DD2DC0386; Sat, 31 Oct 2026 10:56:47 +0100 (CET)
Date: Sat, 31 Oct 2026 10:56:47 +0100
From: Salvatore Bonaccorso <carnil@debian.org>
To: submit@bugs.debian.org
Subject: node-i18next: CVE-2026-63402
Message-ID: <auW7X0l4HyL8SWMM@eldamar.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: carnil
Delivered-To: submit@bugs.debian.org

Source: node-i18next
Version: 23.7.6-2
X-Debbugs-CC: team@security.debian.org
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for node-i18next.

CVE-2026-63402[0]:
| i18next is an internationalization framework for JavaScript. Prior
| to version 26.3.4, `deepExtend` in `src/utils.js` checks property
| existence with the in operator and recurses into inherited built-ins
| reached through `Object.prototype`. An application must explicitly
| pass attacker-controlled resource data to `addResourceBundle(lng,
| ns, data, deep, overwrite)` with both `deep: true` and `overwrite:
| true`. Source keys such as `hasOwnProperty`, `toString` and
| `valueOf` can then select shared inherited built-in function
| objects, and a nested value can overwrite a property of those
| objects process-wide. For example, making
| `Object.prototype.hasOwnProperty.call` non-callable causes
| subsequent uses, including i18next internals, to throw TypeError,
| resulting in unrecoverable denial of service and limited integrity
| impact. The `__proto__`/`constructor` guard does not prevent this
| mechanism because the corruption target is an inherited built-in
| function rather than the prototype object itself. Default calls
| without deep merging or with overwrite falsy are unaffected, and no
| standard i18next backend or integration uses the vulnerable
| configuration. This issue is distinct from the setPath/key-walking
| prototype-pollution flaws in i18next-fs-backend (CVE-2026-48713) and
| i18next-http-middleware (CVE-2026-48714). This issue is fixed in
| version 26.3.4.


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-63402
    https://www.cve.org/CVERecord?id=CVE-2026-63402
[1] https://github.com/i18next/i18next/security/advisories/GHSA-6jcc-5g8w-32mx
[2] https://github.com/i18next/i18next/commit/642137b7786d83661ec3ee53027798dc4b81d30a

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]