# CVE-2026-48713: i18next-fs-backend: Prototype pollution via crafted missing-key string

> Prototype pollution in i18next-fs-backend allows attackers to modify global object properties via crafted missing-key strings when missing-key persistence is enabled.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-2933-q333-qg83, MINI-c3g2-64h6-xx6r, MINI-f58r-w5rv-w66w

## What is CVE-2026-48713?

CVE-2026-48713 is a critical code injection vulnerability in i18next-fs-backend, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions prior to 2.6.6 are vulnerable to prototype pollution via crafted missing-key strings when used to persist missing translation keys (e.g. via i18next-http-middleware's missingKeyHandler exposed to untrusted input). 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. Applications are affected only if the missingKeyHandler (or another route that forwards untrusted request bodies to i18next.t(..., { ... }) with saveMissing: true) is reachable by untrusted users and 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. This issue has been fixed in version 2.6.6. If developers using the library are unable to upgrade immediately, they should take the following precautions: 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, and set keySeparator: false in their i18next options to disable backend key splitting (note: this also disables nested translation keys).

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-48713?

2 open source packages ship an affected version, including i18next-fs-backend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `i18next-fs-backend` | npm | All versions | 2.6.6 |
| `i18next-fs-backend` | npm | All versions | 2.6.6 |

Products: I18next I18next-Fs-Backend.

## How do I fix CVE-2026-48713?

Upgrade i18next-fs-backend to 2.6.6 or later.

## Is CVE-2026-48713 being exploited?

There is no known exploitation of CVE-2026-48713 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48713 and fix it if it is affected.

What it is: CVE-2026-48713 is a critical code injection vulnerability in i18next-fs-backend, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48713 in the wild and no public exploit code.

Affected packages and fixed versions:
- i18next-fs-backend (npm): affected all versions; fixed in 2.6.6
- i18next-fs-backend (npm): affected all versions; fixed in 2.6.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48713/ (Markdown: https://insights.sbomify.com/CVE-2026-48713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48713
- OSV: https://osv.dev/vulnerability/CVE-2026-48713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48713/
Summaries are generated and may contain mistakes; the official description above is the record.