CVE-2026-41691: i18next-http-backend has Path Traversal & URL Injection via Unsanitised lng/ns

Published May 7, 2026
·
Updated

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).

Affected Software

7 affected componentsFixes available
npm/i18nextify<3.0.5
npm/i18next-http-backend
i18next I18next-http-backend Node.js<3.0.5
IBM Business Automation Insights<=24.0.0
IBM Business Automation Insights<=24.0.1
IBM Business Automation Insights<=25.0.0
IBM Business Automation Insights<=26.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade i18nextify to a version that resolves this vulnerability.

    Fixed in 3.0.5
  2. Configuration

    For versions prior to 3.0.5, sanitise user-controlled language inputs (lng and ns) before they reach i18next/i18next-http-backend: strip .., /, \ , ?, #, %, whitespace, and control characters, and cap length, so lng/ns cannot alter the structure of the outgoing URL template.

    i18nextify / i18next-http-backend interpolateUrl sanitisation for lng and ns = Strip/neutralize .., /, \ , ?, #, %, whitespace, and control characters and cap the length before interpolating into loadPath/addPath templates

Event History

May 7, 2026
CVE Published
via MITRE·08:09 PM
Data Sourced
via MITRE·08:09 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 5, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-41691?

CVE-2026-41691 is rated as a high-severity vulnerability due to its potential for path traversal and URL injection.

2

How do I fix CVE-2026-41691?

To fix CVE-2026-41691, upgrade the i18next-http-backend and i18nextify libraries to version 3.0.5 or later.

3

What types of attacks can CVE-2026-41691 facilitate?

CVE-2026-41691 can facilitate attacks such as path traversal and URL injection, potentially exposing sensitive data.

4

Which versions of i18next-http-backend are affected by CVE-2026-41691?

All versions of i18next-http-backend prior to the patch are affected by CVE-2026-41691.

5

What is i18nextify in relation to CVE-2026-41691?

i18nextify is a JavaScript library that is affected by CVE-2026-41691 due to its integration with i18next-http-backend.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203