Low 3.1Published Oct 23, 2026

CVE-2026-115730i18next-http-backend 4.0.2 Protocol-Relative URL Injection via Namespace in interpolateUrl

Updated under an hour ago (Oct 28, 2026, 5:25 PM ET)

Does this affect you?

It affects i18next-http-backend. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for i18next-http-backend

Exploited in the last 30 days

i18next-http-backend 4.0.2 contains an incomplete fix in interpolateUrl() that allows attackers to redirect translation requests by supplying an ns value starting with a slash. Attackers controlling the namespace value can form a protocol-relative URL in loadPath or addPath templates to load attacker-hosted translations, enabling UI content injection and cross-site scripting.

CVSS: 3.1 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness (CWE): CWE-74
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Awaiting Analysis
Record last updated: Oct 23, 2026
First seen by InfoSec Signals: Oct 23, 2026

Affected products

Affected products

i18next i18next-http-backend i18next:http_backend (from the name)	from 4.0.2 before 4.0.3	CNA record

References

References

https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-9jhj-wvmw-cfx5	vendor-advisory
https://github.com/i18next/i18next-http-backend/commit/042c3d4e4e9d73b2ae3aa76b22cb45d48f1e35b7	patch
https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-xvq9-wjp8-hwqf	related, vendor-advisory
https://www.vulncheck.com/advisories/i18next-http-backend-4.0.2-protocol-relative-url-injection-via-namespace-in-interpolateurl	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.