Description
i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno. Prior to 4.0.2, attacker-controlled language or namespace values interpolated into a custom loadPath or addPath that begins directly with {{lng}} or {{ns}} can make colon-based input become an absolute URL or, in browsers, make a double-slash namespace become a protocol-relative URL. The resulting request can leave the intended origin and cause URL injection or server-side request forgery. The default /locales/{{lng}}/{{ns}}.json template and templates with a leading path or origin are not affected because the placeholder does not occupy the URL's structural beginning. This issue is fixed in version 4.0.2.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| i18next | i18next-http-backend | < 4.0.2 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | node-i18next-http-backend | No fix yet | — |
| Debian 13 | node-i18next-http-backend | No fix yet | — |
| Debian 12 | node-i18next-http-backend | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | node-i18next-http-backend | No fix yet | — |
| Ubuntu 26.04 LTS | node-i18next-http-backend | No fix yet | — |
| Ubuntu 24.04 LTS | node-i18next-http-backend | No fix yet | — |
| Ubuntu 22.04 LTS | node-i18next-http-backend | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | i18next-http-backend | < 4.0.2 | 4.0.2 | GHSA-xvq9-wjp8-hwqf |