Live › vulnerability › CVE-2026-63402
i18next's deepExtend, reached through addResourceBundle with deep and overwrite both true, can follow inherited Object.prototype built-ins such as hasOwnProperty, so attacker-supplied resource data overwrites them process-wide. The result is denial of service through TypeErrors across the application, with limited integrity impact.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 23:26 UTC. All times on this page are UTC.
Only applications that call addResourceBundle with deep set to true and overwrite set to true, and pass attacker-controlled resource data into it. Default calls, calls without deep merging, and calls with overwrite off are unaffected, and no standard i18next backend or integration uses this configuration. Teams that load translations only from their own bundled files can skip it.
No product ranges from the sources yet.
npm ls i18next to find the installed version and whether it is below 26.3.4.addResourceBundle( that pass deep and overwrite as true with data that comes from users or external input.26.3.4 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-63402")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.