← Back
CVE-2026-48714
critical
CVSS 9.1
Vulnerability in i18next-http-middleware (CVE-2026-48714)
Summary
vulnerability in i18next-http-middleware (CVE-2026-48714). Data can be tampered with by attackers. Exploitable via ``missingKeyHandler``. Mitigation: upgrade to `3.9.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48714** has been found in i18next-http-middleware.
Attackers can target a specific entry point like ``missingKeyHandler`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade i18next-http-middleware to **3.9.7** or later.
If unsure, ask your IT team or search "i18next-http-middleware CVE-2026-48714" on the vendor's site.
CVE-2026-48714 (i18next-http-middleware) — CWE-1321 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `missingKeyHandler` / `__proto__` / `constructor` / `prototype`
Patched: `3.9.7` — apply immediately
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
**A vulnerability** (CWE-1321) exists in i18next-http-middleware. Attackers reach the vulnerable code path via ``missingKeyHandler`` without authentication.
📍 Affected scope
i18next-http-middleware — . Attack surface: `missingKeyHandler` / `__proto__` / `constructor` / `prototype`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **3.9.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'i18next-http-middleware' .` 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-http-middleware' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `i18next-http-middleware` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade i18next-http-middleware to 3.9.7ステージング環境で 3.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
i18next-http-middleware
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.9.7"}]}]
References
- web https://github.com/i18next/i18next-http-middleware/commit/7c6d26f137d3e940b8d229ca148bca38845faf49
- web https://github.com/i18next/i18next-http-middleware/security/advisories/GHSA-f49m-vf83-692w
- web https://nvd.nist.gov/vuln/detail/CVE-2026-48714
- web https://github.com/advisories/GHSA-f49m-vf83-692w