CVE-2026-41693: i18next-fs-backend: Path traversal via unsanitised lng/ns allows arbitrary file read/overwrite

Published May 8, 2026
·
Updated

i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem. Prior to version 2.6.4, i18next-fs-backend substitutes the lng and ns options directly into the configured loadPath / addPath templates and then read / write the resulting file from disk. The interpolation is unencoded and unvalidated, so a crafted lng or ns value — containing .., a path separator, a control character, a prototype key, or simply an unexpectedly long string — allows an attacker who can influence either value to read or overwrite files outside the intended locale directory. When lng / ns are derived from untrusted input (request-scoped i18next instances behind an HTTP layer such as i18next-http-middleware, or any framework that lets the end user pick the language via query string, cookie, or header), a single request such as ?lng=../../../../etc/passwd causes the backend to attempt to read that path. This issue has been patched in version 2.6.4.

Affected Software

2 affected components
npm/i18next-fs-backend<2.6.4
IBM API Connect V12 OnPrem<=All

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade i18next-fs-backend to a version that resolves this vulnerability.

    Fixed in 2.6.4
  2. Compensating control

    If you create request-scoped i18next instances behind an HTTP layer (e.g., i18next-http-middleware) or allow users to set lng/ns via query string, cookie, or header, ensure lng and ns are validated/sanitized and restricted to an allowlist of expected locale names before passing them to i18next-fs-backend.

Event History

May 8, 2026
CVE Published
via MITRE·03:38 PM
Data Sourced
via MITRE·03:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Jul 7, 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-41693?

CVE-2026-41693 has a high severity due to its potential for arbitrary file read and overwrite.

2

How do I fix CVE-2026-41693?

To fix CVE-2026-41693, upgrade i18next-fs-backend to version 2.6.4 or later.

3

What versions are affected by CVE-2026-41693?

CVE-2026-41693 affects all versions of i18next-fs-backend prior to version 2.6.4.

4

What type of vulnerability is CVE-2026-41693?

CVE-2026-41693 is a path traversal vulnerability that allows for unsanitized file access.

5

Who is impacted by CVE-2026-41693?

Developers using i18next-fs-backend versions below 2.6.4 are impacted by CVE-2026-41693.

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