i18next-fs-backend is vulnerable to Prototype Pollution
91
Critical Risk
When the backend persists missing translation keys, writeFile splits each missing-key string on the configured keySeparator before calling internal setPath helpers. Crafted keys such as __proto__.polluted were split into path segments that getLastOfPath followed into Object.prototype, letting attackers write properties onto the shared prototype. This is reachable when saveMissing flows accept untrusted input such as i18next-http-middleware missingKeyHandler. The fix blocks descent through __proto__, constructor, or prototype segments and silently drops unsafe writes while leaving legitimate dotted keys intact.
You are affected if you are using a version that falls within the vulnerable range.
i18next-fs-backend is vulnerable to Prototype Pollution in versions 0.0.1 - 2.6.5.
Upgrade the i18next-fs-backend library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant