Intel

AIKIDO-2026-10994

i18next-fs-backend is vulnerable to Prototype Pollution

Prototype PollutionCVE-2026-48713 Published 4 days ago

91

Critical Risk

This Affects:

JSi18next-fs-backend
0.0.1 - 2.6.5
Fixed in 2.6.6
Are you affected? Scan for Free

TL;DR

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.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

i18next-fs-backend is vulnerable to Prototype Pollution in versions 0.0.1 - 2.6.5.

How to fix this

Upgrade the i18next-fs-backend library to the patch version.