CVE Catalog

CVE-2026-41885

MediumCVSS 6.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.22%

13th percentile - higher than 13% of all known CVEs

Summary

i18next-locize-backend interpolates lng, ns, projectId, and version directly into URL templates with no path-component validation and no encoding. When an application exposes these values to user-controlled input, a crafted value can change the structure of the outgoing request URL.

Risk Assessment

Requests may be redirected to unexpected targets or data may be exposed. Risk affects applications using i18next-locize-backend before 9.0.2.

Recommendation

Update i18next-locize-backend to version 9.0.2 or later.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS