CVE-2026-48713

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).

• CWE-1321

• https://github.com/i18next/i18next-fs-backend/commit/3ab0448087da6935a40117f904b7457281f963f4Patch
• https://github.com/i18next/i18next-fs-backend/security/advisories/GHSA-2933-q333-qg83Mitigation, Vendor Advisory

Published

Jun 15, 2026

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-48706Envoy is an open source edge and service proxy designed for …7.5
• CVE-2026-48708OliveTin gives access to predefined shell commands from a we…7.5
• CVE-2026-48709OliveTin gives access to predefined shell commands from a we…3.7
• CVE-2026-4871The Sports Club Management plugin for WordPress is vulnerabl…6.4
• CVE-2026-48710Starlette is a lightweight ASGI framework/toolkit. Prior to …6.5
• CVE-2026-48712protobufjs compiles protobuf definitions into JavaScript (JS…7.5
• CVE-2026-48714i18next-http-middleware is a middleware to be used with Node…9.1
• CVE-2026-48715radvd is a router advertisement daemon for IPv6. Prior to ve…8.8
• CVE-2026-48716nanobot is a personal AI assistant. In versions 0.1.5.post3 …8.7
• CVE-2026-48719Warp is an agentic development environment. From 0.2025.08.0…8
• CVE-2026-4872Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2026-48720Warp is an agentic development environment. From 0.2025.03.0…8.8