i18next-http-backend (npm) has 4 known vulnerabilities, the worst rated MODERATE. Upgrade to 4.0.4 or later to clear all of them. No malicious-package signal is recorded.
Versions of i18next-http-backend prior to 3.0.5 interpolate the lng and ns values directly into the configured loadPath / addPath URL template without any…
// questionsIs i18next-http-backend safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for i18next-http-backend (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does i18next-http-backend have known vulnerabilities?
Yes. CyberXYZ records 4 known vulnerabilities for i18next-http-backend (npm), the worst rated MODERATE. They are GHSA-q89c-q3h5-w34g, GHSA-9jhj-wvmw-cfx5, GHSA-3cmx-xjww-583x, GHSA-xvq9-wjp8-hwqf.
Which version of i18next-http-backend should I use?
4.0.4 or later clears every advisory recorded for i18next-http-backend (npm). Check the release you pick before installing it.
How do I check i18next-http-backend before installing?
Search i18next-http-backend in CyberXYZ Check at https://cyberxyz.io/check?q=i18next-http-backend. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:11 UTC. The most recent advisory here was published 2026-10-28. Updated continuously from NVD, GHSA, OSV and CNA feeds.