Categories
CVE-2026-41885 medium CVSS 6.5

Path Traversal in i18next-locize-backend (CVE-2026-41885)

Summary

Path traversal in i18next-locize-backend (CVE-2026-41885). Risk of unauthorized operations or information disclosure. Exploitable via lng. Mitigation: upgrade to 9.0.2 or later.

Original description

The description as published by the source.

i18next-locize-backend is a simple i18next backend for locize.com which can be used in Node.js, in the browser and for Deno. Prior to version 9.0.2, i18next-locize-backend interpolates lng, ns, projectId, and version directly into the configured loadPath / privatePath / addPath / updatePath / getLanguagesPath URL templates with no path-component validation and no encoding. When an application exposes any of these values to user-controlled input (?lng= / ?ns= query parameters via i18next-browser-languagedetector, cookies, request headers, or a URL-derived projectId), a crafted value can change the structure of the outgoing request URL. Affected call sites in lib/index.js (pre-patch): the interpolate() helper is used at the five URL-build sites — _readAny/read (line 415 for private, 426 for public), getLanguages (lines 271 and 296), and writePage (lines 616 and 622) for the missing-key and update POST paths. The helper interpolate in lib/utils.js substitutes raw values with no encoding. This issue has been patched in version 9.0.2.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41885 has been found in i18next-locize-backend.
Attackers can target a specific entry point like lng over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade i18next-locize-backend to 9.0.2 or later.
If unsure, ask your IT team or search "i18next-locize-backend CVE-2026-41885" on the vendor's site.

CVE-2026-41885 (i18next-locize-backend) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: lng / projectId / version / loadPath
Patched: 9.0.2 — apply immediately
Workaround: No workaround short of upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in i18next-locize-backend. Attackers reach the vulnerable code path via lng without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of i18next-locize-backend. Attack surface: lng / projectId / version / loadPath.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 9.0.2.

🛡️ Workaround

Workaround: No workaround short of upgrading.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'i18next-locize-backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'i18next-locize-backend' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で i18next-locize-backend を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    No workaround short of upgrading.

    パッチが適用されるまでの応急処置として、No workaround short of upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade i18next-locize-backend to 9.0.2

    ステージング環境で 9.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm i18next-locize-backend
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"9.0.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details