CVE-2026-41691 json
i18next-http-backend has Path Traversal & URL Injection via Unsanitised lng/ns
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also GHSA-q89c-q3h5-w34g , EUVD-2026-28438
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
Copilot said: i18nextify is a JavaScript library that adds i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions prior to 3.0.5 interpolate the lng and ns values directly into the configured loadPath / addPath URL template without any encoding, validation, or path sanitisation. When an application exposes the language-code selection to user-controlled input (the default — i18next-browser-languagedetector reads ?lng= query params, cookies, localStorage, and request headers), an attacker can inject characters that change the structure of the outgoing request URL. This is a single URL-injection vulnerability. The attacker-controlled value is neutralised before it is used as part of an output URL string; the attack shape covers both path traversal and broader URL-structure injection — both are closed by the one interpolateUrl sanitisation fix. This issue has been fixed in version 3.0.5. If users cannot upgrade immediately, they can work around the issue by sanitising lng / ns before they reach i18next (strip .., /, \, ?, #, %, whitespace, and control characters; cap the length).
Patch / fix
- npm i18next-http-backend 3.0.5
- i18next i18next-http-backend 3.0.5
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | i18next-http-backend | <3.0.5 |
3.0.5 |
Affected products
- i18next i18next-http-backend
Classification
References
-
github.com
/i18next/i18next-http-backend/commit/4cee84f229c637b9c182366d3156f726d407a621
web, patch
-
github.com
/i18next/i18next-http-backend/security/advisories/GHSA-q89c-q3h5-w34g
web, mitigation, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-41691
advisory
-
github.com
/i18next/i18next-http-backend
package
Sources
- CVE List CVE-2026-41691
- GitHub Advisory GHSA-q89c-q3h5-w34g
- NVD CVE-2026-41691
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.