CVE-2026-48713: I18next fs backend I18next-fs-backend Vulnerable To Prototype Pollution Vulnerability

CRITICAL
Advisory Identifier: GHSA-2933-q333-qg83
CVSS 9.1
CWE-1321
Published
Advisory Summary

CVE-2026-48713 is a CRITICAL (CVSS 9.1) i18next-fs-backend vulnerable to prototype pollution vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting I18next fs backend libraries in the npm ecosystem. The issue involves i18next-fs-backend vulnerable to prototype pollution via crafted missing-key string. Remediation is available by upgrading affected packages to version 2.6.6.

CVE-2026-48713 at a Glance

CVE Identifier CVE-2026-48713
GHSA Identifier GHSA-2933-q333-qg83
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product I18next fs backend
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-48713

To remediate this vulnerability, upgrade all affected I18next fs backend dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

i18next-fs-backend fixed: 2.6.6
npm install i18next-fs-backend@2.6.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls i18next-fs-backend

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-48713, inspect your project dependencies using npm:

npm ls i18next-fs-backend

Analyze the terminal output to locate any version of I18next fs backend in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.6.6), your application is affected.

Note: The npm ls i18next-fs-backend command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where the product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. In I18next fs backend, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `i18next-fs-backend` ≤ 2.6.5, when used to persist missing translation keys (e.g. via `i18next-http-middleware`'s `missingKeyHandler` exposed to untrusted input), is vulnerable to prototype pollution via crafted missing-key strings. `Backend.writeFile()` splits each queued missing-key string on the configured `keySeparator` (default `.`) before calling the internal `setPath()` walker. The walker (`getLastOfPath` in `lib/utils.js`) did not guard against unsafe segments, so a key like `"__proto__.polluted"` was split into `["__proto__", "polluted"]` and walked straight into `Object.prototype`, allowing an attacker to write arbitrary properties onto the global object prototype. Depending on the host application, polluted prototype properties may cause crashes, corrupted translation behaviour, configuration poisoning, or bypasses of property-based security checks. ### Affected configuration Applications are directly affected only if **all** of the following hold: - `i18next-fs-backend` ≤ 2.6.5 is configured as the backend. - `i18next-http-middleware`'s `missingKeyHandler` (or another route that forwards untrusted request bodies to `i18next.t(..., { ... })` with `saveMissing: true`) is reachable by untrusted users. - The default behaviour of splitting missing-key strings on `keySeparator` is in use (i.e. `keySeparator` is not `false`). Apps that do not expose missing-key persistence to untrusted input are not directly affected through this attack path. ### Patches Fixed in **i18next-fs-backend 2.6.6**. The traversal helper now refuses to descend through `__proto__`, `constructor`, or `prototype` segments and drops the offending write silently. Legitimate dotted keys (e.g. `"header.title"`) are unaffected. A matching defence-in-depth fix has been shipped in `i18next-http-middleware` **3.9.7** — see the companion advisory. ### Workarounds If users cannot upgrade immediately: - Do not expose `i18next-http-middleware`'s `missingKeyHandler` to untrusted users (mount it behind authentication, or remove the route). - Disable missing-key persistence (`saveMissing: false`, or no `backend.create` implementation) when accepting writes from untrusted input. - Set `keySeparator: false` in the i18next options to disable backend key splitting (note: this also disables nested translation keys). ### Resources - Original report by [@codeswhite](https://github.com/codeswhite). - Companion advisory in `i18next-http-middleware`: [GHSA-f49m-vf83-692w](https://github.com/i18next/i18next-http-middleware/security/advisories/GHSA-f49m-vf83-692w). - Previous `i18next-fs-backend` security release: GHSA-8847-338w-5hcj (path traversal via `lng`/`ns`, fixed in 2.6.4).

CVE-2026-48713 Affected I18next fs backend Versions

1 component(s)
Fixed Versions:
2.6.6
Product / Package Ecosystem Affected Versions Fixed Version
i18next-fs-backend
npm
< 2.6.6
2.6.6

References

Frequently Asked Questions

What is CVE-2026-48713?
CVE-2026-48713 is a security vulnerability in I18next fs backend involving i18next-fs-backend vulnerable to prototype pollution via crafted missing-key string under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which I18next fs backend versions are affected?
Affected versions include releases prior to 2.6.6 across affected packages: i18next-fs-backend.
What version fixes CVE-2026-48713?
Upgrading to 2.6.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is i18next-fs-backend affected?
Yes, i18next-fs-backend is affected in releases prior to 2.6.6. Upgrade your dependency to 2.6.6 or later.
What is the CVSS score of CVE-2026-48713?
CVE-2026-48713 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-48713?
CVE-2026-48713 is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.).
How can I check npm dependencies for CVE-2026-48713?
Run the dependency tree command: 'npm ls i18next-fs-backend'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2933-q333-qg83",
  "modified" : "2026-06-25T17:28:46Z",
  "published" : "2026-06-25T17:28:46Z",
  "aliases" : [ "CVE-2026-48713" ],
  "summary" : "i18next-fs-backend vulnerable to prototype pollution via crafted missing-key string",
  "details" : "### Impact\n\n`i18next-fs-backend` ≤ 2.6.5, when used to persist missing translation keys (e.g. via `i18next-http-middleware`'s `missingKeyHandler` exposed to untrusted input), is vulnerable to prototype pollution via crafted missing-key strings.\n\n`Backend.writeFile()` splits each queued missing-key string on the configured `keySeparator` (default `.`) before calling the internal `setPath()` walker. The walker (`getLastOfPath` in `lib/utils.js`) did not guard against unsafe segments, so a key like `\"__proto__.polluted\"` was split into `[\"__proto__\", \"polluted\"]` and walked straight into `Object.prototype`, allowing an attacker to write arbitrary properties onto the global object prototype.\n\nDepending on the host application, polluted prototype properties may cause crashes, corrupted translation behaviour, configuration poisoning, or bypasses of property-based security checks.\n\n### Affected configuration\n\nApplications are directly affected only if **all** of the following hold:\n\n- `i18next-fs-backend` ≤ 2.6.5 is configured as the backend.\n- `i18next-http-middleware`'s `missingKeyHandler` (or another route that forwards untrusted request bodies to `i18next.t(..., { ... })` with `saveMissing: true`) is reachable by untrusted users.\n- The default behaviour of splitting missing-key strings on `keySeparator` is in use (i.e. `keySeparator` is not `false`).\n\nApps that do not expose missing-key persistence to untrusted input are not directly affected through this attack path.\n\n### Patches\n\nFixed in **i18next-fs-backend 2.6.6**. The traversal helper now refuses to descend through `__proto__`, `constructor`, or `prototype` segments and drops the offending write silently. Legitimate dotted keys (e.g. `\"header.title\"`) are unaffected.\n\nA matching defence-in-depth fix has been shipped in `i18next-http-middleware` **3.9.7** — see the companion advisory.\n\n### Workarounds\n\nIf users cannot upgrade immediately:\n\n- Do not expose `i18next-http-middleware`'s `missingKeyHandler` to untrusted users (mount it behind authentication, or remove the route).\n- Disable missing-key persistence (`saveMissing: false`, or no `backend.create` implementation) when accepting writes from untrusted input.\n- Set `keySeparator: false` in the i18next options to disable backend key splitting (note: this also disables nested translation keys).\n\n### Resources\n\n- Original report by [@codeswhite](https://github.com/codeswhite).\n- Companion advisory in `i18next-http-middleware`: [GHSA-f49m-vf83-692w](https://github.com/i18next/i18next-http-middleware/security/advisories/GHSA-f49m-vf83-692w).\n- Previous `i18next-fs-backend` security release: GHSA-8847-338w-5hcj (path traversal via `lng`/`ns`, fixed in 2.6.4).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "i18next-fs-backend"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.6.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/i18next/i18next-fs-backend/security/advisories/GHSA-2933-q333-qg83"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48713"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/i18next/i18next-fs-backend/commit/3ab0448087da6935a40117f904b7457281f963f4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/i18next/i18next-fs-backend"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-25T17:28:46Z",
    "nvd_published_at" : "2026-06-15T22:16:17Z"
  }
}