Description
Verified on 4.0.2 (latest on npm) and on commit 07e0288 (the GHSA-xvq9-wjp8-hwqf fix). Earlier 3.x/4.x versions that allow / in ns are likely affected too. Not verified on them.
Recommendation
Update the i18next-http-backend package to the latest compatible version. Followings are version details:
- Affected version(s): < 4.0.3
- Patched version(s): 4.0.3
References
Could your website be exposed too?
SmartScanner can check your website for i18next-http-backend: Namespace value starting with / forms a protocol-relative URL when loadPath/addPath places {{ns}} and gives you actionable findings to investigate.
Start a free scanRelated Issues
- i18next-http-backend: Query-parameter injection through & and = in lng when loadPath/addPath puts {{lng}} in the query s - CVE-2026-118258
- i18next-http-backend incomplete URL validation permits SSRF - CVE-2026-105800
- i18next-http-backend has Path Traversal & URL Injection via Unsanitised lng/ns - CVE-2026-41691
- Nitro has an Open Redirect via Protocol-Relative URL Bypass in Wildcard Route Rules - CVE-2026-44372
You might also like:
See something that needs correcting? Let us knowUpdated October 29, 2026