← Back
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.
AI summary snake-internal / snake-material-v2
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
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'i18next-locize-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `i18next-locize-backend` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
No workaround short of upgrading.パッチが適用されるまでの応急処置として、No workaround short of upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade i18next-locize-backend to 9.0.2ステージング環境で 9.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
i18next-locize-backend
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"9.0.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41885
- package https://github.com/locize/i18next-locize-backend
- web https://github.com/locize/i18next-locize-backend/security/advisories/GHSA-mgcp-mfp8-3q45
- web https://github.com/locize/i18next-locize-backend/commit/8f81ad4707aa0e90647fde4da5fbe5b23153c6e1
- web https://github.com/locize/i18next-locize-backend/releases/tag/v9.0.2
- web https://github.com/advisories/GHSA-mgcp-mfp8-3q45