CVE-2026-41885
CVE-2026-41885 · Path traversal / URL injection via unsanitised lng/ns/projectId/version in i18next-locize-backend
This page contains facts from public vulnerability sources. Check the original advisory before updating.
i18next-locize-backend is a simple i18next backend for locize.com which can be used in Node.js, in the browser and for Deno. Prior to version 9.0.2, i18next-locize-backend interpolates lng, ns, projectId, and version directly into the configured loadPath / privatePath / addPath / updatePath / getLanguagesPath URL templates with no path-component validation and no encoding. When an application exposes any of these values to user-controlled input (?lng= / ?ns= query parameters via i18next-browser-languagedetector, cookies, request headers, or a URL-derived projectId), a crafted value can change the structure of the outgoing request URL. Affected call sites in lib/index.js (pre-patch): the interpolate() helper is used at the five URL-build sites — _readAny/read (line 415 for private, 426 for public), getLanguages (lines 271 and 296), and writePage (lines 616 and 622) for the missing-key and update POST paths. The helper interpolate in lib/utils.js substitutes raw values with no encoding. This issue has been patched in version 9.0.2.
CVSS 6.5 · Medium · EPSS 0.2% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
i18next-locize-backend
- Versions
- < 9.0.2: Affected
No fix published
i18next-locize-backend npm
- Affected ranges
- SEMVER: < 9.0.2
Update to 9.0.2